-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a better status message #1492
Add a better status message #1492
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #1492 +/- ##
=======================================
Coverage 61.63% 61.64%
=======================================
Files 138 137 -1
Lines 10294 10371 +77
=======================================
+ Hits 6345 6393 +48
- Misses 3436 3461 +25
- Partials 513 517 +4
☔ View full report in Codecov by Sentry. |
lgtm |
81b006c
to
7c0cbe7
Compare
variable: | ||
|
||
* `{{ namespace }}`: The target namespace where the pipelinerun is executed | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a example format how it looks like after adding {{ namespace }}
I mean something similar to what added in custom-console-url-pr-details
example: https://mycorp.com/ns/{{ namespace }}/pipelinerun/{{ pr }}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
what do you mean for openshift? you only need this if you have a custom console and do not use the openshift console, you can have a custom console when running on openshift
@@ -250,6 +250,16 @@ A few settings are available to configure this feature: | |||
|
|||
Set this to the root URL of your custom console. example: `https://mycorp.com` | |||
|
|||
* `custom-console-url-namespace` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I mean i tried manually i don't see Namespace and PR name in details 🤔
7c0cbe7
to
db79ade
Compare
/retest |
We are adding a better status message that will include the Namespace and the PipelineRun. We link the Namespace to the Namespace view in the consoles. Introducing a new setting for that `custom-console-url-namespace` that would need to be setup when using a custom console. Signed-off-by: Chmouel Boudjnah <[email protected]>
db79ade
to
d30554f
Compare
/test linters |
I installed this PR on dogfooding cluster you can see the example here: https://github.com/openshift-pipelines/pipelines-as-code/pull/1492/checks?check_run_id=18482061202 redid most of the test reconciler to test this properly (it didn't before) with golden |
We are adding a better status message that will include the Namespace and the PipelineRun.
We link the Namespace to the Namespace view in the consoles.
Introducing a new setting for that
custom-console-url-namespace
that would need to be setup when using a custom console.Changes
Submitter Checklist
make test
before submitting a PR (ie: with pre-commit, no need to waste CPU cycle on CI. (or even better install pre-commit and dopre-commit install
in the root of this repo).make lint
before submitting a PR. The markdownlint error can get usually fixed by runningmake fix-markdownlint
(make sure it's installed first)