[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Maxime Lemanissier edited a comment on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing I'm having a similar issue using pipeline library.When i merge a change on the master branch of my jenkins pipeline library, all jobs using this library (more than 100...) are also all rebuilt simultaneously, which fills Jenkins queue for hours everytime a change is made on the library. .. This default behavior is probably well intended, as if the pipeline changes, all jobs using should be rebuilt, but when having a lot of jobs, this becomes unpractical/unusable. I would prefer to wait for the next manual build or SCM change on the project repository (not on the lib one) to trigger a new build. Is there a way to not trigger builds due to changes on the pipeline library?If not, can i use a specific naming convention for the master branch of the pipeline library, and excluding it from polling as shared in previous comment? Will this exclusion also apply on pipeline library? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Maxime Lemanissier commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing I'm having a similar issue using pipeline library. When i merge a change on the master branch of my jenkins pipeline library, all jobs using this library (more than 100...) are also rebuilt simultaneously, which fills Jenkins queue for hours everytime a change is made on the library. This default behavior is probably well intended, as if the pipeline changes, all jobs using should be rebuilt, but when having a lot of jobs, this becomes unpractical/unusable. Is there a way to not trigger builds due to changes on the pipeline library? If not, can i use a specific naming convention for the master branch of the pipeline library, and excluding it from polling as shared in previous comment? Will this exclusion also apply on pipeline library? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier
commented on JENKINS-24970
Blank page when reapproving
I made a last test. If I post to http://myCIServer/jenkins/job/test_promotion_1/5/promotion/promotionProcess/tag-live/promotionCondition/hudson.plugins.promoted_builds.conditions.ManualCondition/approve a form with data json={} and Submit=approve, the promotion is run successfully. But if I resend this exact post, I get back http://myCIServer/jenkins/job/test_promotion_1/5/promotion and no further promotion build is run.
I'm not sure why reapprovals are not using the same mechanism than first approval but that might explain why formers are not working in my case.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier commented on JENKINS-24970 Blank page when reapproving The html forms for approving or re-approving are also quite different. For first approval, the form is For next approvals (which produce blank page), the form is This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier commented on JENKINS-24970 Blank page when reapproving One precision that might be important : this user does not have the 'promote' permission (though he's able to run the promotion using the button 'approve' - button 'force promotion' is not displayed) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier reopened JENKINS-24970 Blank page when reapproving Hi Daniel, Thanks for the link to JENKINS-22550. I have upgraded GHPRB plugin to 1.16-1 and I don't get the NoSuchMethodError anymore, but I still get the blank page when I re-execute a promotion. In my case, a given promotion with manual approval can only be run once on a given build. Change By: Maxime Lemanissier (03/Oct/14 8:47 AM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier
updated JENKINS-24970
Blank page when reapproving
Change By:
Maxime Lemanissier
(02/Oct/14 4:00 PM)
Description:
Hi, i'm running with Jenkins 1.559 and promoted builds plugin 2.17.In a job with a promotion process defined with a manual approval, the first execution of the promotion on a build (by clicking 'approve' button) is successful, but the next ones (by clicking on 'Re-execute promotion' button) return a blank http page, and produces this exception in Jenkins log:
{code} Error while serving http://ci-server/jenkins/job/test_promotion_1/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCronjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1135.invoke(Unknown Source)(snip) Caused by: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at org.jenkinsci.plugins.ghprb.GhprbTrigger$DescriptorImpl.doCheckCron(GhprbTrigger.java:349){code} The problem is not reproducible when i use an admin user.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier
updated JENKINS-24970
Blank page when reapproving
Change By:
Maxime Lemanissier
(02/Oct/14 4:00 PM)
Description:
Hi, i'm running with Jenkins 1.559 and promoted builds plugin 2.17.In a job with a promotion process defined with a manual
approbation
approval
, the first execution of the promotion on a build (by clicking 'approve' button) is successful, but the next ones (by clicking on 'Re-execute promotion' button) return a blank http page, and produces this exception in Jenkins log:{code} Error while serving http://ci-server/jenkins/job/test_promotion_1/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCronjava.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1135.invoke(Unknown Source)(snip) Caused by: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at org.jenkinsci.plugins.ghprb.GhprbTrigger$DescriptorImpl.doCheckCron(GhprbTrigger.java:349){code} The problem is not reproducible when i use an admin user.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24970) Blank page when reapproving
Maxime Lemanissier created JENKINS-24970 Blank page when reapproving Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 02/Oct/14 3:43 PM Description: Hi, i'm running with Jenkins 1.559 and promoted builds plugin 2.17. In a job with a promotion process defined with a manual approbation, the first execution of the promotion on a build (by clicking 'approve' button) is successful, but the next ones (by clicking on 'Re-execute promotion' button) return a blank http page, and produces this exception in Jenkins log: Error while serving http://ci-server/jenkins/job/test_promotion_1/descriptorByName/org.jenkinsci.plugins.ghprb.GhprbTrigger/checkCron java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1135.invoke(Unknown Source) (snip) Caused by: java.lang.NoSuchMethodError: hudson.triggers.TimerTrigger$DescriptorImpl.doCheckSpec(Ljava/lang/String;)Lhudson/util/FormValidation; at org.jenkinsci.plugins.ghprb.GhprbTrigger$DescriptorImpl.doCheckCron(GhprbTrigger.java:349) The problem is not reproducible when i use an admin user. Project: Jenkins Priority: Minor Reporter: Maxime Lemanissier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Maxime Lemanissier commented on JENKINS-21750 Promoted Builds Plugin I don't know if this could help but Promoted build plugin v2.18 introduces a new REST API to manage promotions (fixes https://issues.jenkins-ci.org/browse/JENKINS-8963). Maybe DSL plugin could use it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Maxime Lemanissier edited a comment on JENKINS-21750 Promoted Builds Plugin Hi, I was migrating to DSL plugin to manage all our CI and release jobs (~400) when I discovered that promotions are not yet supported, which is a blocker to implement our build pipeline. In my case, promotions are configured in template jobs. Jobs created using these templates get any empty 'promotion' folder. That would be great to support this. Here is the link to Thomas' pull request (additional discussion in it) that may help to track progress on this subject : https://github.com/jenkinsci/job-dsl-plugin/pull/157 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Maxime Lemanissier commented on JENKINS-21750 Promoted Builds Plugin Hi, I was migrating to DSL plugin to manage all our CI and release jobs (~400) when I discovered that promotions are not yet supported, which is a blocker in my case to implement our build pipeline. Here is the link to Thomas' pull request (additional discussion in it) that may help others to track progress on this subject : https://github.com/jenkinsci/job-dsl-plugin/pull/157 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17051) Inconsistent latest build
Maxime Lemanissier commented on JENKINS-17051 Inconsistent latest build The status of the job is also computed with this strange latest build. With the setting of the attached screenshot, the job is green instead of yellow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17051) Inconsistent latest build
Maxime Lemanissier created JENKINS-17051 Inconsistent latest build Issue Type: Bug Assignee: Unassigned Attachments: jenkins build list.png Components: core Created: 04/Mar/13 2:11 PM Description: Hi all, I'm facing a strange behaviour in Jenkins (currently 1.473 but also got on previous version). Sometimes the list of builds for a given job displays a build that does not exist. This build has a build number much higher than the real one (so it appears at the top of the build list) and its date is in the past. See attached screenshot. After a while, this strange build appears twice. If I hit refresh, only one strange build is displayed, and after few seconds this second strange build reappears... The data on the file system looks good: ci@factory-server-01:/data/workspaces/jenkins/data/jobs/iprod-ci_common-test/builds$ ls -lt total 120 drwxr-xr-x 2 ci ci 4096 2013-03-04 14:40 2013-03-04_14-32-05 lrwxrwxrwx 1 ci ci 19 2013-03-04 14:32 1383 -> 2013-03-04_14-32-05 drwxr-xr-x 2 ci ci 4096 2013-03-04 14:32 2013-03-04_14-31-44 lrwxrwxrwx 1 ci ci 19 2013-03-04 14:31 1382 -> 2013-03-04_14-31-44 drwxr-xr-x 2 ci ci 4096 2013-03-04 14:29 2013-03-04_14-22-52 lrwxrwxrwx 1 ci ci 19 2013-03-04 14:22 1381 -> 2013-03-04_14-22-52 drwxr-xr-x 2 ci ci 4096 2013-03-04 14:21 2013-03-04_14-21-18 lrwxrwxrwx 1 ci ci 19 2013-03-04 14:21 1380 -> 2013-03-04_14-21-18 ... ci@factory-server-01:/data/workspaces/jenkins/data/jobs/iprod-ci_common-test$ cat nextBuildNumber 1384 ci@factory-server-01:/data/workspaces/jenkins/data/jobs/iprod-ci_common-test$ ll last* lrwxrwxrwx 1 ci ci 26 2013-03-04 14:40 lastStable -> builds/2013-03-04_14-32-05/ lrwxrwxrwx 1 ci ci 26 2013-03-04 14:40 lastSuccessful -> builds/2013-03-04_14-32-05/ This strange build is still displayed after a restart of Jenkins. Anyone facing this? Project: Jenkins Priority: Major Reporter: Maxime Lemanissier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14102) Unstable main build leads to post steps being executed even if configured not to
Maxime Lemanissier commented on JENKINS-14102 Unstable main build leads to post steps being executed even if configured not to I get the same error with Jenkins 1.473, Maven build unstable but post steps still executed. I have also tried to pass a -Dmaven.test.failure.ignore=false, the build is then failed but post steps are still executed :/ Is there any planned date/version to get a fix for this annoying problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13631) Can't manually promote build with approval parameter
Maxime Lemanissier commented on JENKINS-13631 Can't manually promote build with approval parameter Problem reproducible with version 2.6, and confirming that it works with 2.4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
