Pipeline-Maven-Plugin when current build status is UNSTABLE

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Pipeline-Maven-Plugin when current build status is UNSTABLE

Benjamin Tocquec
Hi,

Here is my context.
I have a pipeline with main steps:
  • mvn clean deploy
  • mvn test
  • sonar quality gate
I choose to set currentBuild.result = 'UNSTABLE' if last step (quality gate from Sonar) is not OK.
I want my dependencies to build automatically downstream projects when SNAPSHOT.

Everything works well when quality gate is OK (means the job is SUCCESS):
If my newly SUCCESSed project A contains SNAPSHOTed dependencies B, I can see on "Downstream Jobs" of this dependency B the newly build project.
So, when I build this dependency B, on finished, job from project A is launched.

BUT

If my job from project A is UNSTABLE (by choice, forced in my pipeline), it will be no more referenced as a downstream Job from dependency B.
(so building B will no more trigger A)
I'd like this relationship not to be lost :/

Any help appreciated !
Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/165f21fe-fe35-4e56-86ff-27f6e4cd052a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline-Maven-Plugin when current build status is UNSTABLE

Benjamin Tocquec
Finally found the mistake/solution: my Sonar Stage was in a separated node. Groupingg every stages in same node solved my issue.

Thanks

Le jeudi 21 mars 2019 18:59:38 UTC+1, Benjamin Tocquec a écrit :
Hi,

Here is my context.
I have a pipeline with main steps:
  • mvn clean deploy
  • mvn test
  • sonar quality gate
I choose to set currentBuild.result = 'UNSTABLE' if last step (quality gate from Sonar) is not OK.
I want my dependencies to build automatically downstream projects when SNAPSHOT.

Everything works well when quality gate is OK (means the job is SUCCESS):
If my newly SUCCESSed project A contains SNAPSHOTed dependencies B, I can see on "Downstream Jobs" of this dependency B the newly build project.
So, when I build this dependency B, on finished, job from project A is launched.

BUT

If my job from project A is UNSTABLE (by choice, forced in my pipeline), it will be no more referenced as a downstream Job from dependency B.
(so building B will no more trigger A)
I'd like this relationship not to be lost :/

Any help appreciated !
Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2687d2f3-0f43-42fc-a8be-b09dd16305b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline-Maven-Plugin when current build status is UNSTABLE

Benjamin Tocquec
Not really closed !!!!!
For a new project, it won't be added to downstream list of its parent project unless its status is STABLE.

So in my case, when a new project compile but Sonar gate fails, it's marked as UNSTABLE and not present in downstream list of its parent.

Can someone help me please?


Le jeudi 21 mars 2019 20:37:33 UTC+1, Benjamin Tocquec a écrit :
Finally found the mistake/solution: my Sonar Stage was in a separated node. Groupingg every stages in same node solved my issue.

Thanks

Le jeudi 21 mars 2019 18:59:38 UTC+1, Benjamin Tocquec a écrit :
Hi,

Here is my context.
I have a pipeline with main steps:
  • mvn clean deploy
  • mvn test
  • sonar quality gate
I choose to set currentBuild.result = 'UNSTABLE' if last step (quality gate from Sonar) is not OK.
I want my dependencies to build automatically downstream projects when SNAPSHOT.

Everything works well when quality gate is OK (means the job is SUCCESS):
If my newly SUCCESSed project A contains SNAPSHOTed dependencies B, I can see on "Downstream Jobs" of this dependency B the newly build project.
So, when I build this dependency B, on finished, job from project A is launched.

BUT

If my job from project A is UNSTABLE (by choice, forced in my pipeline), it will be no more referenced as a downstream Job from dependency B.
(so building B will no more trigger A)
I'd like this relationship not to be lost :/

Any help appreciated !
Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0c413c26-c228-4786-b8e9-377dba4f1a0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline-Maven-Plugin when current build status is UNSTABLE

Cyrille Le Clerc
@Benjamin can you please create a jira issue, it's easier for us to follow up.

On Monday, March 25, 2019 at 9:40:57 AM UTC+1, Benjamin Tocquec wrote:
Not really closed !!!!!
For a new project, it won't be added to downstream list of its parent project unless its status is STABLE.

So in my case, when a new project compile but Sonar gate fails, it's marked as UNSTABLE and not present in downstream list of its parent.

Can someone help me please?


Le jeudi 21 mars 2019 20:37:33 UTC+1, Benjamin Tocquec a écrit :
Finally found the mistake/solution: my Sonar Stage was in a separated node. Groupingg every stages in same node solved my issue.

Thanks

Le jeudi 21 mars 2019 18:59:38 UTC+1, Benjamin Tocquec a écrit :
Hi,

Here is my context.
I have a pipeline with main steps:
  • mvn clean deploy
  • mvn test
  • sonar quality gate
I choose to set currentBuild.result = 'UNSTABLE' if last step (quality gate from Sonar) is not OK.
I want my dependencies to build automatically downstream projects when SNAPSHOT.

Everything works well when quality gate is OK (means the job is SUCCESS):
If my newly SUCCESSed project A contains SNAPSHOTed dependencies B, I can see on "Downstream Jobs" of this dependency B the newly build project.
So, when I build this dependency B, on finished, job from project A is launched.

BUT

If my job from project A is UNSTABLE (by choice, forced in my pipeline), it will be no more referenced as a downstream Job from dependency B.
(so building B will no more trigger A)
I'd like this relationship not to be lost :/

Any help appreciated !
Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/38eefc06-9f8b-4643-b780-c2c805bfdc6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Pipeline-Maven-Plugin when current build status is UNSTABLE

Benjamin Tocquec
Done: https://issues.jenkins-ci.org/browse/JENKINS-57108

Le mercredi 17 avril 2019 11:20:55 UTC+2, Cyrille Le Clerc a écrit :
@Benjamin can you please create a jira issue, it's easier for us to follow up.

On Monday, March 25, 2019 at 9:40:57 AM UTC+1, Benjamin Tocquec wrote:
Not really closed !!!!!
For a new project, it won't be added to downstream list of its parent project unless its status is STABLE.

So in my case, when a new project compile but Sonar gate fails, it's marked as UNSTABLE and not present in downstream list of its parent.

Can someone help me please?


Le jeudi 21 mars 2019 20:37:33 UTC+1, Benjamin Tocquec a écrit :
Finally found the mistake/solution: my Sonar Stage was in a separated node. Groupingg every stages in same node solved my issue.

Thanks

Le jeudi 21 mars 2019 18:59:38 UTC+1, Benjamin Tocquec a écrit :
Hi,

Here is my context.
I have a pipeline with main steps:
  • mvn clean deploy
  • mvn test
  • sonar quality gate
I choose to set currentBuild.result = 'UNSTABLE' if last step (quality gate from Sonar) is not OK.
I want my dependencies to build automatically downstream projects when SNAPSHOT.

Everything works well when quality gate is OK (means the job is SUCCESS):
If my newly SUCCESSed project A contains SNAPSHOTed dependencies B, I can see on "Downstream Jobs" of this dependency B the newly build project.
So, when I build this dependency B, on finished, job from project A is launched.

BUT

If my job from project A is UNSTABLE (by choice, forced in my pipeline), it will be no more referenced as a downstream Job from dependency B.
(so building B will no more trigger A)
I'd like this relationship not to be lost :/

Any help appreciated !
Thanks!

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9548def6-a82f-4934-82aa-15713f44b353%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.