[JIRA] (JENKINS-36866) Pipeline is started after Jenkins restart
Title: Message Title
mszalbach created an issue
Jenkins / JENKINS-36866
Pipeline is started after Jenkins restart
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-pipeline-plugin, subversion-plugin
Created:
2016/Jul/22 5:36 AM
Environment:
Jenkins ver. 2.13 Build Pipeline Plugin 2.2 SUbversion Plugin 2.6
Priority:
Minor
Reporter:
mszalbach
I used a simple pipeline with two stages like this:
node {
def mvnHome = tool 'Maven-3.3.9'
stage 'Checkout'
svn '/trunk/'
stage 'Build'
sh "${mvnHome}/bin/mvn clean package"
step([$class: 'JUnitResultArchiver', testResults: '**/target/surefire-reports/TEST-*.xml'])
stage 'Analysis'
def sonarProperties='***'
sh "${mvnHome}/bin/mvn $sonarProperties test sonar:sonar"
}
As Build Trigger I use Poll SCM for every minute (* * * * *). However each time I update a plugin and restart Jenkins via the web gui the Job is started even no changes are committed. However the polling log will say "Changes found" and has the same revision as the last build (which was triggered correctly because of a change). All non Pipeline jobs with same polling setup did not rerun after a restart.
[JIRA] (JENKINS-35998) No issue update if at least one issue does not exists
Title: Message Title Sumesh kk edited a comment on JENKINS-35998 Re: No issue update if at least one issue does not exists I am also stuck with this :( JIRA extension plugin updates the issues even if a bad issue is present in the commit message ,but it needs to have the JIRA Project keys hard coded to the tool configuration Should be a REST behaviour Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35998) No issue update if at least one issue does not exists
Title: Message Title Sumesh kk commented on JENKINS-35998 Re: No issue update if at least one issue does not exists I am also stuck with this JIRA extension plugin updates the issues even if a bad issue is present in the commit message ,but it needs to have the JIRA Project keys hard coded to the tool configuration Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-28902) Error displaying report: sidepanel.jelly not found
Title: Message Title Peter Han commented on JENKINS-28902 Re: Error displaying report: sidepanel.jelly not found Andreas Schoenfeld have you solved this issue ? cause I meet the same problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36865) Stage view showing wrong pipeline data
Title: Message Title
Antonio Beyah updated an issue
Jenkins / JENKINS-36865
Stage view showing wrong pipeline data
Change By:
Antonio Beyah
After running a few pipeline executions, if you delete the job and recreate it will show the proper pipeline while building, but after the pipeline has completed running it will revert to showing the pipeline from the previous (deleted) run. After looking at the code to the plugin, I was able to determine that there was a cache and found some code in the tests to invalidate it. I was able to workaround the issue by running the following code in the script console:{code: groovy java }import com.cloudbees.workflow.flownode.FlowNodeUtilFlowNodeUtil.CacheExtension ext = FlowNodeUtil.CacheExtension.all().get(0);ext.getExecutionCache().invalidateAll();ext.getRunCache().invalidateAll();{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To
[JIRA] (JENKINS-36865) Stage view showing wrong pipeline data
Title: Message Title Antonio Beyah created an issue Jenkins / JENKINS-36865 Stage view showing wrong pipeline data Issue Type: Bug Assignee: Sam Van Oort Attachments: pipeline_stage_view_bug_after_clearing_cache.png, pipeline_stage_view_bug_before.png Components: pipeline-stage-view-plugin Created: 2016/Jul/22 3:19 AM Environment: Jenkins 2.11, Pipeline Stage View v1.6, CentOS 7 Priority: Minor Reporter: Antonio Beyah After running a few pipeline executions, if you delete the job and recreate it will show the proper pipeline while building, but after the pipeline has completed running it will revert to showing the pipeline from the previous (deleted) run. After looking at the code to the plugin, I was able to determine that there was a cache and found some code in the tests to invalidate it. I was able to workaround the issue by running the following code in the script console: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml import com.cloudbees.workflow.flownode.FlowNodeUtil FlowNodeUtil.CacheExtension ext = FlowNodeUtil.CacheExtension.all().get(0);
[JIRA] (JENKINS-36864) git tag patterns not handled like cli git
Title: Message Title Mark Waite commented on JENKINS-36864 Re: git tag patterns not handled like cli git I'm the one who will look at it. I have a large backlog of other pull requests to evaluate, and am targeting to release Jacob Keller's work on submodule authentication in time for Jenkins World 2016 (Sep 2016). Thus, it may be a month or two before I evaluate the pull request. You can increase the chances of my evaluating the pull request by writing tests of the modified methods, by not making white space changes, and by assuring that the plugin behaves well with your changes during interactive testing. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36864) git tag patterns not handled like cli git
Title: Message Title Will Saxon edited a comment on JENKINS-36864 Re: git tag patterns not handled like cli git Hello Mark @markewaite , I have a patchset for this which I am about to submit a PR for. Will you look at it, or will I need to wait for someone else to discover/grab the issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36864) git tag patterns not handled like cli git
Title: Message Title Will Saxon commented on JENKINS-36864 Re: git tag patterns not handled like cli git Hello Mark, I have a patchset for this which I am about to submit a PR for. Will you look at it, or will I need to wait for someone else to discover/grab the issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36864) git tag patterns not handled like cli git
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-36864 git tag patterns not handled like cli git Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36864) git tag patterns not handled like cli git
Title: Message Title Will Saxon created an issue Jenkins / JENKINS-36864 git tag patterns not handled like cli git Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2016/Jul/22 2:18 AM Environment: git client plugin 1.19.6 Priority: Minor Reporter: Will Saxon When filtering a list of tags with 'git tag -l' or 'git ls-remote --tags' on the command line, multiple space-delimited patterns may be specified. See git-tag. This does not work with the Jenkins git-client-plugin. The pattern list is processed as a single parameter; while using the Git Parameter plugin to try and present a list of tags using two tag patterns, I got no tags. According to git-check-ref-format, spaces are not a valid character for git references. So it should be safe to split any passed-in patterns and iterate over them. Add Comment
[JIRA] (JENKINS-31384) Redirect to login page on all 404s without discover permission
Title: Message Title James Roper commented on JENKINS-31384 Re: Redirect to login page on all 404s without discover permission > Would a custom 404 response, that always offered to log in anonymous users, help? I.e. irrespective of whether the requested URL can be handled or would be 404 for every logged in user. If you reread my issue description, you'll see that's essentially what I'm proposing - show the a login page in both cases. The only difference is in the implementation detail, you're saying in both cases the response code will be 404 with a login page rendered, I'm saying in both cases the response code will be a redirect to the login page. From a user experience perspective, they're the same, and from a security perspective, neither gives out any more or less information to people that shouldn't have that information. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32987) Support configurable ID for developer profile
Title: Message Title Denys Digtiar edited a comment on JENKINS-32987 Re: Support configurable ID for developer profile Pull Added a link to pull request which seems to be adding backend changes necessary to implement this feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32987) Support configurable ID for developer profile
Title: Message Title Denys Digtiar commented on JENKINS-32987 Re: Support configurable ID for developer profile Pull request which seems to be adding backend changes necessary to implement this feature. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36862) Jira plugin does not work inside promotion block
Title: Message Title Bella N updated an issue Jenkins / JENKINS-36862 Jira plugin does not work inside promotion block Change By: Bella N Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36860) Add support to select matrix selection from previous build
Title: Message Title Rick Liu commented on JENKINS-36860 Re: Add support to select matrix selection from previous build From Jenkins ICON, it looks like there are 5 different status to represent the previous build status of a matrix cell: Success Failed Success - skipped Failed - skipped Not run "24" height="24" tooltip="Success " src="" class="code-quote" style="color: #009100">"/static/54ffa35b/images/24x24/blue.png" alt="Success" style="" title="Success "> "24" height="24" tooltip="Failed " src="" class="code-quote" style="color: #009100">"/static/ebce1237/images/24x24/red.png" alt="Failed" style="" title="Failed "> "24" height="24" tooltip="Success - skipped" src="" class="code-quote" style="color: #009100">"/static/54ffa35b/images/24x24/blue.png" alt="Success" style="opacity:0.5" title="Success - skipped"> "24" height="24" tooltip="Failed - skipped" src="" class="code-quote" style="color: #009100">"/static/ebce1237/images/24x24/red.png" alt="Failed" style="opacity:0.5" title="Failed - skipped"> "24" height="24" tooltip="Not run" src="" class="code-quote" style="color: #009100">"/static/54ffa35b/images/24x24/grey.png" alt="Not run" title="Not run"> I'd guess if I could enhance the `if-else` block in `drawMainBall()` from `./src/main/resources/hudson/plugins/matrix_configuration_parameter/MatrixCombinationsParameterDefinition/index.groovy`, and update the _javascript_ function `click2Change()` in `drawMainLinksJS()`, then this probably could work? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36863) [Gitlab plugin] Credentials drop-down doesn't show API token credential!
Title: Message Title Tyrel Haveman created an issue Jenkins / JENKINS-36863 [Gitlab plugin] Credentials drop-down doesn't show API token credential! Issue Type: Bug Assignee: Robin Müller Components: gitlab-plugin Created: 2016/Jul/21 11:46 PM Environment: Gitlab Plugin 1.3.0. Jenkins 2.7.1 hosted on Windows 7 64-bit, Java 1.8 64-bit. Client is Chrome 51 on Windows 10 Labels: git gitlab Priority: Blocker Reporter: Tyrel Haveman On Manage Jenkins -> Configure System, in the Gitlab section, there's a Credentials section that had a drop-down list where I should be able to specify an API Token. The drop down says "-none" and has no other options. If I choose Add -> Jenkins, then under Kind I can select "GitLab API token" and put in the info, and click Add. But the credential I've added does not show up in the drop-down, so I can't select it, and I have the red "API Token for Gitlab access required" message. I expect to be able to see the API token credential I have added in the drop-down list so I can select it and connect. But it is not there. As a result I am unable to use the plugin at all.
[JIRA] (JENKINS-36837) Split BlueOcean Jenkins Pipeline API in to separate module
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-36837 Split BlueOcean Jenkins Pipeline API in to separate module Change By: Vivek Pandey Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-18435) Navigating back, then forward, from a job configuration causes loss of config data
Title: Message Title recampbell commented on JENKINS-18435 Re: Navigating back, then forward, from a job configuration causes loss of config data rsandell has a PR in review for this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-18435) Navigating back, then forward, from a job configuration causes loss of config data
Title: Message Title recampbell assigned an issue to rsandell Jenkins / JENKINS-18435 Navigating back, then forward, from a job configuration causes loss of config data Change By: recampbell Assignee: rsandell Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-32168) java.lang.NullPointerException when using the bitbucket oauth plugin
Title: Message Title Brian Youngblood commented on JENKINS-32168 Re: java.lang.NullPointerException when using the bitbucket oauth plugin Same issue here with Jenkins ver. 2.7.1 and plugin version 0.4 and 0.5. Jenkins is running with apache proxy pass to jenkins. Might be the issue and will try soon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-7643) "Workspace is offline" on every SCM poll
Title: Message Title Chiara Gelinas commented on JENKINS-7643 Re: "Workspace is offline" on every SCM poll I am seeing this too, interestingly, only on one of the jobs. We run maven builds in Docker containers so there will never be a workspace since the container gets created and destroyed on every build. What looks like a workaround (so far, I did this for the job that was getting a build triggered on every SCM poll - and we have to poll due to firewall, can't use Git webhooks), was to trigger a build on the non-docker build agent. So, I made my job not "Dockerized", forced a build, and then put the Docker configuration back. So far, it hasn't been triggering with the empty workspace error. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36862) Jira plugin does not work inside promotion block
Title: Message Title Bella N created an issue Jenkins / JENKINS-36862 Jira plugin does not work inside promotion block Issue Type: Bug Assignee: Oleg Nenashev Components: jira-plugin, promoted-builds-plugin Created: 2016/Jul/21 11:14 PM Priority: Minor Reporter: Bella N Jira plugin does not work inside promotion block (outside of it works fine) FATAL: Unable to release jira version RELNOTE-5.0.0/RELNOTE: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.jira.VersionReleaser.perform(VersionReleaser.java:33) at hudson.plugins.jira.JiraReleaseVersionUpdaterBuilder.perform(JiraReleaseVersionUpdaterBuilder.java:52) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:344) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:286) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537) at hudson.model.Run.execute(Run.java:1741) at hudson.model.Run.run(Run.java:1679) at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:231) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)enter code here In Jenkins log I see the following exception: RunListener failed java.lang.UnsupportedOperationException at hudson.plugins.promoted_builds.PromotionProcess.isFingerprintConfigured(PromotionProcess.java:430) at
[JIRA] (JENKINS-33907) Git clone fails on slave if master is Java 6, slave is Java 6 or 7 and wildcard in branch name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-33907 Git clone fails on slave if master is Java 6, slave is Java 6 or 7 and wildcard in branch name Change By: Mark Waite Summary: Git clone fails on slave if master is Java 6, slave is Java 6 or 7 and wildcard in branch name Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35831) Developer can favourite a pipeline from the dashboard
Title: Message Title Cliff Meyers resolved as Fixed Jenkins / JENKINS-35831 Developer can favourite a pipeline from the dashboard Change By: Cliff Meyers Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36502) compatibility with snippet generator
Title: Message Title Liam Newman commented on JENKINS-36502 Re: compatibility with snippet generator Jesse Glick,Daniel Spilker Actually, it isn't the constructor that's the issue exactly. It is the fact that the constructor takes a field that doesn't exist as a "public final" field or a public get/set databound member. I have a PR (noted above) that fixes this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Neil Rhine commented on JENKINS-29652 Re: Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin I added another patch to the ticket that retries on more cases. This one will allow for both the eventual joined build to run on both failure and success until all upstream jobs succeed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-29652) Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin
Title: Message Title Neil Rhine updated an issue Jenkins / JENKINS-29652 Rerunning failed Delivery Pipeline stage doesn't enable/disable a manual trigger when using the Join plugin Change By: Neil Rhine Attachment: 002-Join-plugin-fix-to-allow-retry-on-failure.patch Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36860) Add support to select matrix selection from previous build
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-36860 Add support to select matrix selection from previous build Change By: Rick Liu Attachment: Selection_005.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36861) Matrix combination select Successful includes non-successful (skipped) item
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-36861 Matrix combination select Successful includes non-successful (skipped) item Issue Type: Bug Assignee: Unassigned Attachments: Selection_004.png Components: matrix-combinations-parameter-plugin Created: 2016/Jul/21 10:23 PM Environment: Ubuntu 14.04 x86_64 OpenJDK7 Jenkins 2.14 Matrix Configuration Parameter Plugin 1.0.9 Priority: Major Reporter: Rick Liu When click "Select Successful" link, the auto-selection selects not only the Successful matrix variants, "24" height="24" tooltip="Success " src="" class="code-quote" style="color: #009100">"/static/54ffa35b/images/24x24/blue.png" alt="Success" style="" title="Success "> but also includes the matrix variants that's never been built before. "24" height="24" tooltip="Not run" src="" class="code-quote" style="color: #009100">"/static/54ffa35b/images/24x24/grey.png" alt="Not run" title="Not run">
[JIRA] (JENKINS-36860) Add support to select matrix selection from previous build
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-36860 Add support to select matrix selection from previous build Issue Type: Improvement Assignee: Unassigned Attachments: Selection_003.png Components: matrix-combinations-parameter-plugin Created: 2016/Jul/21 9:55 PM Environment: Ubuntu 14.04 x86_64 OpenJDK7 Jenkins 2.14 Matrix Configuration Parameter Plugin 1.0.9 Priority: Major Reporter: Rick Liu Currently, the matrix-combinations-parameter plugin could support 4 auto-selection: Successful Failed All None I'd like to have the 5th auto-selection "Previous" to be able to select based on the previous build selection. Add Comment
[JIRA] (JENKINS-36502) compatibility with snippet generator
Title: Message Title Daniel Spilker commented on JENKINS-36502 Re: compatibility with snippet generator The problem seems to be the @DataBoundConstructor parameter with type javaposse.jobdsl.plugin.ExecuteDslScripts.ScriptLocation. https://github.com/jenkinsci/job-dsl-plugin/blob/job-dsl-1.48/job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/ExecuteDslScripts.java#L143 Jesse Glick: is there a chance to improve the snippet generator? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27729) Dependency and licence information are not bundled
Title: Message Title Kanstantsin Shautsou commented on JENKINS-27729 Re: Dependency and licence information are not bundled Thanks for details. The link is `/about` it allows list installed plugins and libs with their used licenses. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36753) missing license information in about page
Title: Message Title Daniel Spilker commented on JENKINS-36753 Re: missing license information in about page That information is provided by the maven-license-plugin which has not been ported to Gradle yet. https://github.com/jenkinsci/plugin-pom/blob/plugin-2.11/pom.xml#L702-L744 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36859) EZ-Templates not compatible with jobs created with the MultiBranch plugin
Title: Message Title Michael Fowler created an issue Jenkins / JENKINS-36859 EZ-Templates not compatible with jobs created with the MultiBranch plugin Issue Type: Bug Assignee: Marc Carter Components: ez-templates-plugin Created: 2016/Jul/21 9:30 PM Priority: Critical Reporter: Michael Fowler When you try to use a template based of a multi branch job type, the resulting project has parameters and nothing else is populated. https://wiki.jenkins-ci.org/display/JENKINS/Branch+API+Plugin Add Comment
[JIRA] (JENKINS-33093) Support new feature of upcoming Gradle Plugin 1.25
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.49. Jenkins / JENKINS-33093 Support new feature of upcoming Gradle Plugin 1.25 Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36746) Jenkins 2.7.1 for debian-stable install fails: Size mismatch
Title: Message Title Elwin Andriol commented on JENKINS-36746 Re: Jenkins 2.7.1 for debian-stable install fails: Size mismatch Thank you for that extra context, Daniel. I was not aware of that, mostly because I just started using Jenkins. It does confirm my personal findings, so at least I'm glad about that. I would not argue too quickly that this problem is less worse that the original problem though. Because currently, and this has apparently so far still not been fixed at all, depending on where you are located and what mirror gets selected for downloading the deb package (which appears to be a process that a user has no control over), Jenkins can simply not be installed at all (at least not through the preferred apt-get install method). I would like to stress that such a show stopper (because that is really what it is if the official instruction fail to work) can be very damaging to the first impressions of Jenkins to potential new users. That should not be underestimated IMHO. I happen to be the type that does not like to give up that quickly, but if a particular percentage (I do not know how many mirrors are actually out of sync) of all Debian users who recently tried to install Jenkins have come to the conclusion that this is just impossible, then it could even end up damaging the reputation of Jenkins as a whole (which is of course unrelated in reality, but that might not matter). From here on, I think the most important step would be to first make sure that all mirrors get synced ASAP. As for the future, I think that my suggestion to use a packaging version suffix the same way that Debian does for upstream maintained packages, might still not be such a bad idea. This way, changes in files that are not part of the upstream content can still be versioned. The convention here is to add a dash to the upstream version and then a packaging iteration number to it. So, the 2.7.1 package of Jenkins would have been generated as respectively: jenkins_2.7.1-1_all.deb jenkins_2.7.1-2_all.deb With such a naming scheme, even with mirrors out of sync, the current problem would not exist and Jenkins could still be installed (even if outdated). Of course, the issue with mirrors being out of sync is still a problem that needs to be address for its own obvious reasons. What so far worries me most though, is that apparently nobody is seriously taking up this problem. This problem has now existed for a week and I would not call this just a minor issue. The fact that it got unnoticed for a while is understandable (though it could be argued that proper CI would have prevented that as well). But after I filed this bug report, I still did not see much happening to have this issue swiftly resolved, by somebody with the required privileges to do so. This does in fact worry me. I would not mind putting in effort to resolve this issue, but I expect that I just don't have the required knowledge and neither the credentials for it. Of course, I could just have stumbled on that single or just a few obscure mirrors that are out of sync and only causing me problems (I tried installs from both The Netherlands and from Serbia), but until that is established as a fact, I personally would treat this problem as potentially big and rather serious one.
[JIRA] (JENKINS-36858) Allow plugins to consume the less from the JDL
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36858 Allow plugins to consume the less from the JDL Issue Type: Task Assignee: Cliff Meyers Components: blueocean-plugin Created: 2016/Jul/21 8:57 PM Priority: Minor Reporter: James Dumay Cliff pointed out we have lots of useful mixin's in the JDL less that would be very useful to use in projects consuming the JDL Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-31384) Redirect to login page on all 404s without discover permission
Title: Message Title Daniel Beck commented on JENKINS-31384 Re: Redirect to login page on all 404s without discover permission The behavior as described only applies to instances that grant Overall/Read to anonymous, right? Otherwise, there will always be a login screen, no matter what URL is accessed. And here's the problem – anonymous with some permissions is a legitimate user, so needs to be treated as such – which includes denying existence of resources that account isn't allowed to view. In fact, there's no way for Jenkins to know whether any given URL would be valid without trying to access it as as SYSTEM. Which could have side effects. In fact, I'm sure that the Discover permission exists exactly to prevent the problem you're describing. (There's no point in granting non-anonymous users Discover permission that I'm aware of.) And if you don't want to do that, then you get the denial of existence. Would a custom 404 response, that always offered to log in anonymous users, help? I.e. irrespective of whether the requested URL can be handled or would be 404 for every logged in user. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis edited a comment on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to ${JOB_NAME}, then I'd set the view mappings to: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... {noformat} Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings.https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locationsLeading to something like this: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...+//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... |Col A2| {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis edited a comment on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to ${JOB_NAME}, then I'd set the view mappings to://OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/...Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings.https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locationsLeading to something like this://OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...+//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... |Col A2|
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-36857) AWS throttling error when saving master config
Title: Message Title
Marcela Carbo created an issue
Jenkins / JENKINS-36857
AWS throttling error when saving master config
Issue Type:
Bug
Assignee:
Jan Roehrich
Components:
amazon-ecs-plugin
Created:
2016/Jul/21 8:36 PM
Priority:
Blocker
Reporter:
Marcela Carbo
We have a growing number of templates and have been getting an error when saving the master config. javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class com.cloudbees.jenkins.plugins.amazonecs.ECSCloud from {"name":"ecs_dev","credentialsId":"14d0a5e4-4635-46a0-82e0-b517d704ef92","regionName":"us-east-1","cluster":"arn:aws:ecs:us-east-1:465257512377:cluster/jenkins","tunnel":":8090","templates":[ {"label":"docker_d","image":"localhost/base_slave","remoteFSRoot":"/home/jenkins","memory":"2048","cpu":"2","entrypoint":"","jvmArgs":"-Xmx256m","privileged":false,"logDriver":""} , {"label":"docker_pet_angular","image":"localhost/portusui","remoteFSRoot":"/home/jenkins","memory":"1024","cpu":"2","entrypoint":"","jvmArgs":"","privileged":false,"logDriver":""} , {"label":"unzipper","image":"localhost/unzipper_77","remoteFSRoot":"/home/jenkins","memory":"512","cpu":"2","entrypoint":"","jvmArgs":"","privileged":false,"logDriver":""} ,{"label":"build_docker","image":"localhost/build_docker","remoteFSRoot":"/home/jenkins","memory":"512","cpu":"2","entrypoint":"","jvmArgs":"","privileged":false,"logDriver":"","mountPoints":[ {"name":"dockersock","sourcePath":"/var/run/docker.sock","containerPath":"/var/run/docker.sock","readOnly":false} , {"name":"docker","sourcePath":"/usr/bin/docker","containerPath":"/usr/bin/docker","readOnly":false} , {"name":"libdevmapper","sourcePath":"/lib64/libdevmapper.so.1.02","containerPath":"/lib64/libdevmapper.so.1.02","readOnly":false} , {"name":"libudev","sourcePath":"/lib64/libudev.so.0","containerPath":"/lib64/libudev.so.0","readOnly":false}
[JIRA] (JENKINS-36856) Cannot delete Bitbucket Team job unless there is a repo already
Title: Message Title Isaac Cohen created an issue Jenkins / JENKINS-36856 Cannot delete Bitbucket Team job unless there is a repo already Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Jul/21 8:35 PM Environment: Bitbucket Branch Source Plugin: 1.3 Jenkins 1.642 Priority: Major Reporter: Isaac Cohen When a new Bitbucket Team/Project is created with no repos, it is not possible to delete the Job. Only after a valid repo was entered and a scan was done did the "Delete Folder" button show up. Steps to reproduce: Create a new Bitbucket Team/Project Leave the Repo info blank and just click Save on the configuration screen There is no Delete Folder button visible Go back to the configuration page and enter a valid repo After the Folder scan completes, the Delete Folder button will be visible
[JIRA] (JENKINS-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis edited a comment on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to ${JOB_NAME}, then I'd set the view mappings to: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... {noformat} Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings.https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locationsLeading to something like this: {noformat} //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME}/...+//OSSLEV3/Dev_R4/MNGP/... //${JOB_NAME}/... {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-36746) Jenkins 2.7.1 for debian-stable install fails: Size mismatch
Title: Message Title Elwin Andriol updated an issue Jenkins / JENKINS-36746 Jenkins 2.7.1 for debian-stable install fails: Size mismatch Change By: Elwin Andriol Component/s: packaging Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36746) Jenkins 2.7.1 for debian-stable install fails: Size mismatch
Title: Message Title Daniel Beck commented on JENKINS-36746 Re: Jenkins 2.7.1 for debian-stable install fails: Size mismatch Context, in case you're unaware: https://jenkins.io/blog/2016/07/14/2-7-1-re-release/ TBH I'd rather have this problem than that one… still, we need to look into better handling of this case going forward. First time we ever needed something like this AFAIK. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them.!snapshot4.jpeg|thumbnail!The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI.!snapshot5.jpeg|thumbnail!In my case, it fails since the withEnv wrapper will be null. Build 11 started working again because I removed the withEnv function from my pipeline test. However, entries seem to have a significant delay when loading in the BlueOcean UI. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them. !snapshot4.jpeg|thumbnail! The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI. !snapshot5.jpeg|thumbnail!!snapshot6.jpeg|thumbnail! In my case, it fails since the withEnv wrapper will be null. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them.!snapshot4.jpeg|thumbnail!The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI.!snapshot5.jpeg|thumbnail! !snapshot6.jpeg|thumbnail! In my case, it fails since the withEnv wrapper will be null. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin Attachment: snapshot6.jpeg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin Attachment: snapshot4.jpeg Attachment: snapshot5.jpeg Attachment: snapshot6.jpeg Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin created an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/21 7:18 PM Priority: Major Reporter: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them. The failed build also won't show up the BlueOcean queue, but it will in the standard Jenkins UI. In my case, it fails since the withEnv wrapper will be null. Add Comment
[JIRA] (JENKINS-36855) BlueOcean Not Honoring Parameters For Pipeline Projects
Title: Message Title Mark Austin updated an issue Jenkins / JENKINS-36855 BlueOcean Not Honoring Parameters For Pipeline Projects Change By: Mark Austin BlueOcean will not prompt for parameters when you schedule a pipeline build that requires them. The failed build also won't show up in the BlueOcean pipeline queue, but it will in the standard Jenkins UI. In my case, it fails since the withEnv wrapper will be null. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36426) How to poll two different folder under a single branch in single job
Title: Message Title
Jason Davis commented on JENKINS-36426
Re: How to poll two different folder under a single branch in single job
You could just create a workspace that has the folders you want and either manage that in P4V or in Jenkins. Personally, I'd rather have a different workspace tuned for what I want rather than sharing it, just so I know the purpose of the workspace. For me, I like to keep the workspaces in Jenkins, so I set the Perforce config in the Job to "Manual", then set the name to $ {JOB_NAME}, then I'd set the view mappings to: //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME} /... //OSSLEV3/Dev_R4/MNGP/... //$ {JOB_NAME}/... Jenkins will automatically create a workspace for you with the name of your Jenkins job. btw - Perforce by default doesn't like mapping two different depot paths to the same place, leading to a similar problem you've described. To get around that you'll probably need to use overlay mappings. https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.configuration.html#configuration.refine_workspace.map_diff_depot_locations Leading to something like this: //OSSLEV3/Dev_R4/Cramer/... //${JOB_NAME} /... +//OSSLEV3/Dev_R4/MNGP/... //$ {JOB_NAME} /...
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-36725) Not able to travese XML in pipeline project
Title: Message Title Smithesh Purushothaman commented on JENKINS-36725 Re: Not able to travese XML in pipeline project Sam Van Oort You can close the issue. This was the issue with scripts not getting executed and throws RejectedExeception if "Use Groovy Sandbox" is checked Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title David Walter updated an issue Jenkins / JENKINS-36853 pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty Change By: David Walter Environment: containerized jenkins running version > 2 + Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title David Walter updated an issue Jenkins / JENKINS-36853 pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty Change By: David Walter Component/s: build-pipeline-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36852) Dashboard should use JWT to find the authenticated user
Title: Message Title Vivek Pandey commented on JENKINS-36852 Re: Dashboard should use JWT to find the authenticated user James Dumay yes. UI should do the following: Get Token :https://docs.google.com/document/d/1LrsK4w-PRbQu8aBJXxoaFEvxRjlpIo1Z1k4Sr68ALuY/edit#heading=h.v53y1dtwbdla Verify token and get claim/get user form it: https://docs.google.com/document/d/1LrsK4w-PRbQu8aBJXxoaFEvxRjlpIo1Z1k4Sr68ALuY/edit#heading=h.jw9apl15qatm Call REST API using JWT token: https://docs.google.com/document/d/1LrsK4w-PRbQu8aBJXxoaFEvxRjlpIo1Z1k4Sr68ALuY/edit#heading=h.8opwdiuo6i4k some references: https://jwt.io/ https://github.com/kjur/jsrsasign Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36854) Multi Branch project only adds the first SCM source to the generated jobs
Title: Message Title Martin Weber created an issue Jenkins / JENKINS-36854 Multi Branch project only adds the first SCM source to the generated jobs Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Jul/21 6:30 PM Priority: Major Reporter: Martin Weber My project is set up to monitor and check out from 2 SCM sources of Git-type. While polling works as expected, the generated jobs use only the first SCM source. As a workaround, I tried to add a single Single Repository-type source with 'Mutiple SCMs', but then the SCM-selection list is empty (may a bug in scm-api-plugin) Add Comment
[JIRA] (JENKINS-16170) Ability for the plugin to auto-install Unity3d
Title: Message Title Brantone commented on JENKINS-16170 Re: Ability for the plugin to auto-install Unity3d Sadly, with Unity 5, and how they shifted to a "customized modules" setup, this makes it extremely tricky. They've said they're coming up with alternatives to accomplish it, but haven't seen anything yet. We run a farm of 20+ nodes and a dozen versions simultaneously across 10+ projects so have been working with Unity to accomplish this but it's slow going Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title
David Walter updated an issue
Jenkins / JENKINS-36853
pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Change By:
David Walter
Calling cancel on job step waiting on input terminates normally , both curl POST or hubot http . post Calling proceedEmpty fails with exception: input/ApproveDeployment/proceedEmpty . Using curl POST or hubot POST both fail. {{Stack tracejavax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876}} Even if data is added to the post it continues to fail.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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
[JIRA] (JENKINS-36853) pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Title: Message Title
David Walter created an issue
Jenkins / JENKINS-36853
pipeline input step throws error when reply of input/ApproveDeployment/proceedEmpty
Issue Type:
Bug
Assignee:
Sergei Egorov
Components:
pipeline-view-plugin
Created:
2016/Jul/21 6:10 PM
Environment:
jenkins running 2+
Priority:
Minor
Reporter:
David Walter
Calling cancel on job step waiting on input terminates normally. Calling proceedEmpty fails with exception: input/ApproveDeployment/proceedEmpty {{Stack trace javax.servlet.ServletException: java.lang.IndexOutOfBoundsException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876}}
Add Comment
[JIRA] (JENKINS-34722) Unbounded searches with BuildUtil.getDownstreamBuild
Title: Message Title Andrew Buckles commented on JENKINS-34722 Re: Unbounded searches with BuildUtil.getDownstreamBuild Hi, a bit more information here with regards to the pipeline we are having issues with. Total number of potential jobs for the pipeline is 17... however, each one of those jobs has a range of build history in the thousands (some 8-9K, some 5K and others have 1-2K). The pipeline is configured to only show the last 100 builds, however, will Jenkins still attempt to load all of the build history for each of the jobs involved in the pipeline? For instance, what we observe with a standard job is that Jenkins will take a significant amount of time to load a job page if there are 8000 builds in the build history versus 100-200. Even though Jenkins won't display all of the build history, it still seems to load all of them into memory. Does the pipeline job loading/rendering do a similar style of data fetch for each job in the pipeline? Thanks, Andy Buckles Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36491) Jenkins uses wrong JDK for Maven build step
Title: Message Title Dzianis Mazuronak updated an issue Jenkins / JENKINS-36491 Jenkins uses wrong JDK for Maven build step Change By: Dzianis Mazuronak Environment: Solaris 10 x86, Jenkins 2.11 , Linux x86_64 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-16327) Pages with CodeMirror editors are impossibly wide
Title: Message Title Ollie ! edited a comment on JENKINS-16327 Re: Pages with CodeMirror editors are impossibly wide Adding "max-width: 550px" to the .CodeMirror-scroll class inside codemirror.css will enable the desired and expected behavior. 750px 550px is just an approximate - if someone has a better value, feel free to share it.EDIT: changed 750px to 550px after some experimentation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36845) ConcurrentModificationException when using Xvnc plugin on Pipeline
Title: Message Title Oliver Gondža resolved as Fixed Jenkins / JENKINS-36845 ConcurrentModificationException when using Xvnc plugin on Pipeline Change By: Oliver Gondža Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: James Dumay Google Inbox does this for long email threads In Scope* When the user expands the step the result item sticks to the bottom of the result header . This * User can click on the result item, closes the item and the stickiness to the top cancels out.* Scrolling above or below the expanded item allows you to see the closed result items* Behaviour we want here is almost exactly how ours should work the same as Google Inbox. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title James Dumay stopped work on JENKINS-35864 Change By: James Dumay Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-35864) Step section in log sticks to result header when scrolling
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-35864 Step section in log sticks to result header when scrolling Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36162) Investigate how to break freestyle logs up by step
Title: Message Title James Dumay resolved as Won't Fix Jenkins / JENKINS-36162 Investigate how to break freestyle logs up by step Change By: James Dumay Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36852) Dashboard should use JWT to find the authenticated user
Title: Message Title James Dumay commented on JENKINS-36852 Re: Dashboard should use JWT to find the authenticated user Vivek Pandey is there a guide for frontend developers for using the JWT? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36852) Dashboard should use JWT to find the authenticated user
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36852 Dashboard should use JWT to find the authenticated user Issue Type: Task Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/21 4:28 PM Priority: Minor Reporter: James Dumay This removes an extra call to fetch the authenticated user Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36851) Favourite stars should be hidden for the anonymous user
Title: Message Title James Dumay assigned an issue to Cliff Meyers Jenkins / JENKINS-36851 Favourite stars should be hidden for the anonymous user Change By: James Dumay Assignee: Cliff Meyers Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36851) Favourite stars should be hidden for the anonymous user
Title: Message Title James Dumay commented on JENKINS-36851 Re: Favourite stars should be hidden for the anonymous user Cliff Meyers I also noticed if there are no extension points in that column that we show a blank space for these? Could we make that space go away if there are no extension points? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36851) Favourite stars should be hidden for the anonymous user
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36851 Favourite stars should be hidden for the anonymous user Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Jul/21 4:22 PM Priority: Minor Reporter: James Dumay Favouriting does not work for anonymous users so this action should be hidden from them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-16224) ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations
Title: Message Title Daniel Beck commented on JENKINS-16224 Re: ProjectNamingStrategy/force existing: Does not prevent modifying existing job configurations I think the option should be removed due to unintended side effects, and instead, an e.g. administrative monitor should show admins a list of jobs violating the current job naming pattern. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36850) vSphere keeps info on Slave that has been shutdown / deleted
Title: Message Title Greg Smith created an issue Jenkins / JENKINS-36850 vSphere keeps info on Slave that has been shutdown / deleted Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2016/Jul/21 3:50 PM Environment: Jenkins 2.14 vSphere plugin 2.13 Priority: Minor Reporter: Greg Smith An administrator deleted a slave VM which the vSphere plugin had created dynamically. After that happened, the vSphere plugin continues to believe that this slave is in its list, and is not removing it. Our total number of slave instances is capped – when this happened, we were unable to continue until the cap was raised, as we continued to get this in the logs after the even occurred: There are 1 number of VMs in this bucket. The instance cap for the bucket is: 1 Restarting Jenkins did not resolve the problem. The workaround was to increment our cap to 2, so that one slot was still available. Is there a way to clear the current list of slaves the plugin believes exists? Add Comment
[JIRA] (JENKINS-36724) Branch indexing hangs
Title: Message Title Mandeep kumar edited a comment on JENKINS-36724 Re: Branch indexing hangs I am facing the similar issue and even try to kill these threads ,does not work. Almost every other day ,i am facing this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36724) Branch indexing hangs
Title: Message Title Mandeep kumar updated an issue Jenkins / JENKINS-36724 Branch indexing hangs Change By: Mandeep kumar Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36724) Branch indexing hangs
Title: Message Title Mandeep kumar commented on JENKINS-36724 Re: Branch indexing hangs I am facing the similar issue and even try to kill these threads ,does not work. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34813) SAML2 plugin not working when https is terminated in load balancer
Title: Message Title Rob Sung closed an issue as Not A Defect Jenkins / JENKINS-34813 SAML2 plugin not working when https is terminated in load balancer Change By: Rob Sung Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34813) SAML2 plugin not working when https is terminated in load balancer
Title: Message Title Rob Sung resolved as Not A Defect Figure out this issue and it ended up being issue with Apache configuration on my end. I added "RequestHeader set X-Forwarded-Proto "https"" to the vhost entry and everything worked out correct. Based on the behavior, onelogin appear to be constructing the URL based on who is making the request. Thank you your help. Jenkins / JENKINS-34813 SAML2 plugin not working when https is terminated in load balancer Change By: Rob Sung Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26287) long tasknames in console-outline overlap console output
Title: Message Title wolfs resolved as Fixed Jenkins / JENKINS-26287 long tasknames in console-outline overlap console output Change By: wolfs Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34849) Add tests for Gradle build step
Title: Message Title wolfs closed an issue as Fixed Jenkins / JENKINS-34849 Add tests for Gradle build step Change By: wolfs Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36849) Github organization folder plugin is using only master node
Title: Message Title
Pawel Mucha created an issue
Jenkins / JENKINS-36849
Github organization folder plugin is using only master node
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
github-organization-folder-plugin
Created:
2016/Jul/21 3:02 PM
Environment:
jenkins 2.14 github-orgganization-folder-plugin 1.3 Branch API plugin 1.10 GitHub Branch Source Plugin 1.8.1 Folders Plugin 5.12 Pipeline Multibranch 2.8
Priority:
Major
Reporter:
Pawel Mucha
I have Jenkinsfile with specific node allocation and git checkout on that node, but "github organization folder plugin" is starting build on master and checking out repository on master with default timeout values, before starting my Jenkinsfile script, so I am getting timeouts, because my repository is really big and 10min is simply too small. my Jenkinsfile looks like this:
node("*Not_master_node*")
{
checkout(
[$class: 'GitSCM',
branches: [[name: "${env.BRANCH_NAME}"]],
doGenerateSubmoduleConfigurations: false,
extensions:
[
[$class: 'CleanBeforeCheckout'],
[$class: 'CheckoutOption', timeout: 180],
[$class: 'CloneOption',
depth: 0,
noTags: false,
shallow: true,
timeout: *180*
]
],
submoduleCfg: [],
userRemoteConfigs: [[credentialsId: '...', url: 'https://github.com/...']]]
)
}
[JIRA] (JENKINS-26287) long tasknames in console-outline overlap console output
Title: Message Title wolfs commented on JENKINS-26287 Re: long tasknames in console-outline overlap console output This has been released with 1.25. Please have a look if your problem is solved and then close this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36848) Unable to pass Jenkins status check if GitHub has protected branches
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-36848 Unable to pass Jenkins status check if GitHub has protected branches Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Screenshot 2016-07-21 15.36.00.png, Screenshot 2016-07-21 15.36.28.png Components: github-organization-folder-plugin Created: 2016/Jul/21 2:51 PM Priority: Critical Reporter: Sorin Sbarnea It seems that some updates made in the last two weeks to Jenkins plugins or GitHub api introduce a very strange behaviour on GitHub. Now we can prevent a PR from being merged if a specific Jenkins branch-job is not green but somehow it seems impossible to check if current PR is green. If we do not select any branch in github repository configuration Jenkins build will not happen and the user would be able to merge the change. If we check one of them Jenkins will build it and as a surprise we can see the job name that is matching the PR name. Wonderful, but somehow it seems that the generic check named "Jenkins" is still waiting for another status check, one that will never happen, preventing us from merging.
[JIRA] (JENKINS-26287) long tasknames in console-outline overlap console output
Title: Message Title wolfs assigned an issue to wolfs Jenkins / JENKINS-26287 long tasknames in console-outline overlap console output Change By: wolfs Assignee: youjen li wolfs Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34790) Migrate gradle-plugin to new parent POM and update baseline.
Title: Message Title wolfs closed an issue as Won't Fix Won't fix since the gradle-plugin now uses Gradle to build itself. Jenkins / JENKINS-34790 Migrate gradle-plugin to new parent POM and update baseline. Change By: wolfs Status: In Progress Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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
[JIRA] (JENKINS-34849) Add tests for Gradle build step
Title: Message Title wolfs commented on JENKINS-34849 Re: Add tests for Gradle build step Fixed in 1.25 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34849) Add tests for Gradle build step
Title: Message Title wolfs resolved as Fixed Jenkins / JENKINS-34849 Add tests for Gradle build step Change By: wolfs Status: In Progress Resolved Assignee: Andres Rodriguez wolfs Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34377) job-restrictions does not support Pipeline Plugin
Title: Message Title Daniel Hernandez commented on JENKINS-34377 Re: job-restrictions does not support Pipeline Plugin Handle the users security and forget to verify the security in the "input" step would be a great step Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-34377) job-restrictions does not support Pipeline Plugin
Title: Message Title Daniel Hernandez edited a comment on JENKINS-34377 Re: job-restrictions does not support Pipeline Plugin Handle the users security from Jenkins configuration and forget to verify the security in the "input" step would be a great step :) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27136) Workflow support for GitHub Push Triggers
Title: Message Title Pawel Mucha edited a comment on JENKINS-27136 Re: Workflow support for GitHub Push Triggers 1. In my scenario github-branch-source-plugi is getting timeouts on checkout, because is trying to make checkout with default values (10 min) on master, even that if my pipeline script is using child node and has additional checkout configuration with increased time2. 'Re-register hooks for all jobs' only works if You have admin proviliges for git repo, and in my scenario I am using other company (client) repo, so I wont get it3. Please reopen this feature, because previous two solutions are not working in all cases Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-27136) Workflow support for GitHub Push Triggers
Title: Message Title Pawel Mucha commented on JENKINS-27136 Re: Workflow support for GitHub Push Triggers 1. In my scenario github-branch-source-plugi is getting timeouts on checkout, because is trying to make checkout with default values (10 min) on master, even that my pipeline script is using child node and has additional checkout configuration with increased time 2. 'Re-register hooks for all jobs' only works if You have admin proviliges for git repo, and in my scenario I am using other company (client) repo, so wont get it 3. Please reopen this feature, because previous two solutions are not working in all cases Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36795) hp automation tools - pipeline enabled
Title: Message Title Yafim Kazak edited a comment on JENKINS-36795 Re: hp automation tools - pipeline enabled From the general plugin development view - We have the pipeline support on our plugin road map.As soon as possible, I will post a simple code piece to make it work in the mean time meantime . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-30963) JMeter's Percentage of errors is always 100%
Title: Message Title Marco Piras commented on JENKINS-30963 Re: JMeter's Percentage of errors is always 100% Hi all, i have the same problem. test.jtl I use the version v1.14 of Performance plugin and Jenkins ver. 1.635 I attach the test report file. BR Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-30963) JMeter's Percentage of errors is always 100%
Title: Message Title Marco Piras updated an issue Jenkins / JENKINS-30963 JMeter's Percentage of errors is always 100% Change By: Marco Piras Attachment: test.jtl Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-36648) SSH plugin : no matching cipher found - can't connect to server
Title: Message Title Piotr Rogoża closed an issue as Not A Defect By default JRE provides weak or insufficient cryptographic algorithms*. I've installed JCE Unlimited Strength Jurisdiction Policy Files and I'm able to connect with any host. *) https://docs.oracle.com/javase/7/docs/technotes/guides/security/SunProviders.html#importlimits Jenkins / JENKINS-36648 SSH plugin : no matching cipher found - can't connect to server Change By: Piotr Rogoża Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title Dave Hunt commented on JENKINS-31660 Re: StackOverflowError when maximum number of builds archived Just seen this again after an upgrade to Jenkins 2.7.1. The first build failure after the upgrade was reported as expected, however the next build passed but hit this stack overflow. Disabling Test Stability History in the configuration allowed the build to pass without this exception. I've attached the full console log including the exception: console.log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
