[JIRA] (JENKINS-39238) Add credentials does not save new credential
Title: Message Title Shashank Agrawal edited a comment on JENKINS-39238 Re: Add credentials does not save new credential When I'm hitting save after adding credentials, I'm getting the following error on the browser's console: !Screen Shot 2016-11-01 at 10.44.40 AM.png|thumbnail! Looks like, I'm missing something since it's hitting to the 127.0.0.1. I'm using latest build 2.28 and also updated the "Jenkins URL" field with my EC2 domain 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-39238) Add credentials does not save new credential
Title: Message Title Shashank Agrawal updated an issue Jenkins / JENKINS-39238 Add credentials does not save new credential Change By: Shashank Agrawal Attachment: Screen Shot 2016-11-01 at 10.44.40 AM.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-39238) Add credentials does not save new credential
Title: Message Title Shashank Agrawal edited a comment on JENKINS-39238 Re: Add credentials does not save new credential When I'm hitting save after adding credentials, I'm getting the following error on the browser's console: !Screen Shot 2016-11-01 at 10.44.40 AM.png|thumbnail! Looks like, I'm missing something since it's hitting to the 127.0.0.1 . I'm using latest build 2.28 and also updated the "Jenkins URL" field with my EC2 domain 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Michael Neale Component/s: blueocean-plugin Component/s: pipeline 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Michael Neale NOTE this ticket is to track the linked blocking ticket for the blue ocean project. When there is a build which has a stage that marks the build as unstable, all the stages are marked incorrectly as unstable vs just the unstable stage. Expected action: only the stage that marked the build is unstable should return as such. To reproduce: * Build the multibranch pipeline "kzantow/failure-project" from github* Look at the "michaelneale" branch* Note that all stages are unstable (check the api json, all stages are UNSTABLE but should not be, only the final stage should be).This is the same in stage view as well as stage graph incidentally. 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
[JIRA] (JENKINS-39238) Add credentials does not save new credential
Title: Message Title Shashank Agrawal reopened an issue Jenkins / JENKINS-39238 Add credentials does not save new credential Change By: Shashank Agrawal Resolution: Cannot Reproduce Status: Closed Reopened 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-39238) Add credentials does not save new credential
Title: Message Title Shashank Agrawal updated an issue Jenkins / JENKINS-39238 Add credentials does not save new credential Change By: Shashank Agrawal Attachment: Screen Shot 2016-11-01 at 10.44.40 AM.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-39238) Add credentials does not save new credential
Title: Message Title Shashank Agrawal commented on JENKINS-39238 Re: Add credentials does not save new credential When I'm hitting save after adding credentials, I'm getting the following error on the browser's console:Looks like, I'm missing something since it's hitting to the 127.0.0.1 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-39238) Add credentials does not save new credential
Title: Message Title Shashank Agrawal commented on JENKINS-39238 Re: Add credentials does not save new credential I'm also facing the same issue. Any new credentials I add, they are not being saved. 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-39395) Input cannot be approved on Blue Ocean pipeline UI
Title: Message Title Daniel Ryan updated an issue Jenkins / JENKINS-39395 Input cannot be approved on Blue Ocean pipeline UI Change By: Daniel Ryan Component/s: pipeline-stage-view-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-39395) Input cannot be approved on Blue Ocean pipeline UI
Title: Message Title
Daniel Ryan created an issue
Jenkins / JENKINS-39395
Input cannot be approved on Blue Ocean pipeline UI
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2016/Nov/01 5:05 AM
Environment:
Jenkins ver. 2.19.1 BlueOcean beta io.jenkins.blueocean:blueocean:1.0.0-b10 jdk1.8.0_102 apache-tomcat-8.5.5 CentOS Linux release 7.2.1511 Jenkins is installed as only 1 master node, no slaves.
Priority:
Minor
Reporter:
Daniel Ryan
When a pipeline gets to an "input" step, the blue pipeline UI doesn't give any apparent way to approve the input, and so the pipeline just hangs. Also, when input is the first thing to happen in a pipeline, the UI appears that it hasn't loaded anything and is just waiting. Example pipeline snippets:
stage ('s1') {
echo 'this is stage 1'
}
stage ('s2') {
echo 'this is stage 2'
input id: 'Approve', message: 'Approve', ok: 'Yes'
}
stage ('s3') {
echo 'this is stage 3'
}
Re: [JIRA] (JENKINS-39394) Consistent notification usage between stage-level and top level
Due to how things are implemented at runtime, I don't think we can do aliasing. -- 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-39394) Consistent notification usage between stage-level and top level
Title: Message Title Michael Neale commented on JENKINS-39394 Re: Consistent notification usage between stage-level and top level email-ext is not "broken" in this sense, it lets you attach files from the workspace to an email, which is a useful thing. There is no way to fix that as it needs access to a workspace (if files were archived, it could pick it form there but that seems to be making busy-work). I would be happy if notifications were an alias to postBuild. Its just documenting the pipeline, not behavior. If we have to explain subtle differences then we have already lost. 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-39394) Consistent notification usage between stage-level and top level
Title: Message Title Patrick Wolf commented on JENKINS-39394 Re: Consistent notification usage between stage-level and top level Even if we fix all the plugins like email-ext then we still have inconsistent usage between stage-level and top-level. Email-ext's reliance on a node only compounds this inconsistency. 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-39394) Consistent notification usage between stage-level and top level
Title: Message Title James Dumay commented on JENKINS-39394 Re: Consistent notification usage between stage-level and top level Some plugins like 'email-ext' must be within a node to work and will not work in the notifications section Why is that? How fixable is it? 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-39394) Consistent notification usage between stage-level and top level
Title: Message Title Patrick Wolf created an issue Jenkins / JENKINS-39394 Consistent notification usage between stage-level and top level Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Nov/01 3:53 AM Priority: Minor Reporter: Patrick Wolf We currently have postBuild and notifications sections at the top level of pipeline. It is possible to send notifications in either of them. Notifications in postBuild are sent from a node while notifications within notifications are sent outside of a node. Some plugins like 'email-ext' must be within a node to work and will not work in the notifications section. Within a stage we have only a post section but no notifications section. All notifications within a stage must be done in the post block. This inconsistency between stage-level settings and top-level settings and support for different plugins creates unneeded complexity in trying to document best practices for usage. We should either create a notifications section at the stage level or document how to do notifications with post and postBuild only. cc: Michael Neale James Dumay Add Comment
[JIRA] (JENKINS-39393) When "origin branches also filed as PRs" is set, FileNotFoundException from malformed GitHub "open PR" query
Title: Message Title
G. Richard Bellamy created an issue
Jenkins / JENKINS-39393
When "origin branches also filed as PRs" is set, FileNotFoundException from malformed GitHub "open PR" query
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
github-organization-folder-plugin
Created:
2016/Nov/01 3:25 AM
Environment:
Jenkins: 2.27 Plugin: 1.4 and 1.5
Labels:
github
Priority:
Blocker
Reporter:
G. Richard Bellamy
When trying to re-scan our GitHub Org, and we have set the "Build origin branches also filed as PRs" or really any of the "origin PR" settings, I see the following exception:
Nov 01, 2016 3:02:06 AM SEVERE hudson.model.Executor finish1
Executor threw an exception
java.lang.Error: java.io.FileNotFoundException: {"message":"Server Error","documentation_url":"https://developer.github.com/v3"}
at org.kohsuke.github.Requester$PagingIterator.fetch(Requester.java:433)
at org.kohsuke.github.Requester$PagingIterator.hasNext(Requester.java:400)
at org.kohsuke.github.PagedIterator.fetch(PagedIterator.java:44)
at org.kohsuke.github.PagedIterator.hasNext(PagedIterator.java:32)
at org.kohsuke.github.PagedIterable.asList(PagedIterable.java:42)
at org.kohsuke.github.GHRepository.getPullRequests(GHRepository.java:648)
at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.doRetrieve(GitHubSCMSource.java:381)
at
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title James Dumay reopened an issue We are going to reopen this so the Blue Ocean team can track JENKINS-26522 and verify that it works as expected when it is completed. Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: James Dumay Resolution: Duplicate Status: Resolved Reopened 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
[JIRA] (JENKINS-39255) Timeout 'clean before checkout' configurable
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-39255 Timeout 'clean before checkout' configurable 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-31440) Target SDK should not be a required field
Title: Message Title Ferran Poveda commented on JENKINS-31440 Re: Target SDK should not be a required field Still an issue. Tested on 1.7, Xcode 8, macOS 10.12. 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Michael Neale resolved as Duplicate Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Michael Neale Status: Reopened Resolved Resolution: Duplicate 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-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Michael Neale commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Thanks Sam Van Oort Jesse Glick that explanation makes sense to me, I think I get it now. So yes, in that case, closing this in favour of JENKINS-26522 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-38284) Handle per-stage configuration in declarative
Title: Message Title Andrew Bayer resolved as Fixed Jenkins / JENKINS-38284 Handle per-stage configuration in declarative Change By: Andrew Bayer 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-39245) Support environment section inside stages
Title: Message Title Andrew Bayer updated JENKINS-39245 Jenkins / JENKINS-39245 Support environment section inside stages Change By: Andrew Bayer Status: In Review 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-39244) Support tools section inside agent
Title: Message Title Andrew Bayer updated JENKINS-39244 Jenkins / JENKINS-39244 Support tools section inside agent Change By: Andrew Bayer Status: In Review 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-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Title: Message Title Stephen Rufle commented on JENKINS-20427 Re: Build Parameter variable in branch name causes polling to detect false changes in GIT I have seen this same issue with the TFS plugin used in Jenkins Multiple SCM plugin 0.5 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-39133) Aborting a build can result in an UNKNOWN stage state
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39133 Aborting a build can result in an UNKNOWN stage state Change By: Michael Neale Sprint: indian 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-39133) Aborting a build can result in an UNKNOWN stage state
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-39133 Aborting a build can result in an UNKNOWN stage state Change By: Michael Neale Sprint: arctic 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-39361) LDAP SSL authentication isn't working with OpenJDK 8/Oracle JDK 8
Title: Message Title Rachel Moreno resolved as Not A Defect Hi Alex Grinko, It's a very usual problem when upgrading JVM, because of disabling insecure algorithms. Your certificates were signed by security algorithms that are considered insecure by new version. It could be resolved quickly by commenting with # the line that starts with jdk.certpath.disabledAlgorithms= in JDK_HOME/jre/lib/security/java.security, but I think it's better to renew certificates in order to use another signature algorithm which is accepted by the new version. You can find a lot of articles about this problem when looking for Certificates does not conform to algorithm constraints. I hope be useful. Best regards, Rachel Jenkins / JENKINS-39361 LDAP SSL authentication isn't working with OpenJDK 8/Oracle JDK 8 Change By: Rachel Moreno Status: In Progress Resolved Assignee: Kohsuke Kawaguchi Rachel Moreno Resolution: Not A Defect Add Comment
[JIRA] (JENKINS-39361) LDAP SSL authentication isn't working with OpenJDK 8/Oracle JDK 8
Title: Message Title Rachel Moreno started work on JENKINS-39361 Change By: Rachel Moreno Status: Open In Progress 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-33619) Script definition area rendered over header section
Title: Message Title Daniel Beck resolved as Cannot Reproduce Cannot reproduce either. Notably on my 2.24, the Pipeline input field is no longer resizable, so maybe the component has been changed? Jenkins / JENKINS-33619 Script definition area rendered over header section Change By: Daniel Beck Status: In Progress Resolved Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-39392) don't disable building PRs for Bitbucket Server instances
Title: Message Title mcrooney updated an issue Jenkins / JENKINS-39392 don't disable building PRs for Bitbucket Server instances Change By: mcrooney Currently the plugin checks if the repo is public, and doesn't allow building PRs, "Skipping pull requests for public repositories." While I assume this is for security purposes for Bitbucket.org, it is a problematic limitation for private Bitbucket Server instances that use a PR-based flow and have the repo "Public", which only means it can be viewed and cloned. Only authenticated users can push and create pull requests and we need to be able to discover and test these effectively private pull requests :) 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-39392) don't disable building PRs for Bitbucket Server instances
Title: Message Title mcrooney commented on JENKINS-39392 Re: don't disable building PRs for Bitbucket Server instances Created https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/24 which we'll build and use locally to work around this, feedback/merging welcome 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-38363) Investigate slow loading experience
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-38363 Investigate slow loading experience Change By: James Dumay Assignee: Keith Zantow Tom FENNELLY 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-38363) Investigate slow loading experience
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38363 Investigate slow loading experience Change By: James Dumay Priority: Critical 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-39392) don't disable building PRs for Bitbucket Server instances
Title: Message Title mcrooney created an issue Jenkins / JENKINS-39392 don't disable building PRs for Bitbucket Server instances Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Oct/31 10:05 PM Environment: Jenkins 2.19.1, Bitbucket Branch Source Plugin 1.8 Priority: Minor Reporter: mcrooney Currently the plugin checks if the repo is public, and doesn't allow building PRs, "Skipping pull requests for public repositories." While I assume this is for security purposes for Bitbucket.org, it is a problematic limitation for private Bitbucket Server instances that use a PR-based flow and have the repo "Public", which only means it can be viewed and cloned. Only authenticated users can push and create pull requests and we need to be able to discover and test these pull requests Add Comment
[JIRA] (JENKINS-38584) REST API for fetching available steps
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-38584 REST API for fetching available steps Change By: James Dumay Sprint: atlantic, arctic indian 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-39340) High CPU in doRename
Title: Message Title Brendan Mannix commented on JENKINS-39340 Re: High CPU in doRename The Jenkins Monitoring Plugin provides a convenient way to kill that particular java thread. https://wiki.jenkins-ci.org/display/JENKINS/Monitoring Problem threads (e.g. doRenames) appear in the "Current Requests" list 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-38584) REST API for fetching available steps
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38584 REST API for fetching available steps Change By: Michael Neale Sprint: atlantic , indian 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-38584) REST API for fetching available steps
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-38584 REST API for fetching available steps Change By: Michael Neale Sprint: atlantic , arctic 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-38363) Investigate slow loading experience
Title: Message Title Michael Neale stopped work on JENKINS-38363 Change By: Michael Neale 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-39340) High CPU in doRename
Title: Message Title Brendan Mannix commented on JENKINS-39340 Re: High CPU in doRename I'm seeing the same behavior with OpenJDK 8. openjdk version "1.8.0_102" OpenJDK Runtime Environment (build 1.8.0_102-b14) OpenJDK 64-Bit Server VM (build 25.102-b14, mixed mode) 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-34650) Allow global libraries to bypass the sandbox
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34650 Re: Allow global libraries to bypass the sandbox Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/docker/workflow/DockerDSL.java src/main/java/org/jenkinsci/plugins/docker/workflow/ImageNameTokens.java src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy http://jenkins-ci.org/commit/docker-workflow-plugin/223612bc8378cc3e02cc6fecee1416c5bd533af9 Log: Merge pull request #75 from jglick/GlobalVariable-JENKINS-32731 JENKINS-32731 JENKINS-34650 Docker.groovy is already trusted Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/1f5f9d0147c4...223612bc8378 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-38169) Single parameter steps don't work when using named parameter in workflow-cps 2.14/2.15
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38169 Re: Single parameter steps don't work when using named parameter in workflow-cps 2.14/2.15 Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/docker-workflow-plugin/0e95a7bf7af6d647ed3ebc5d1a6ab8dce5c59549 Log: Actually needed to upgrade a bit further to pick up the fix of JENKINS-38169. 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-29711) Snippet Generator: missing attribute names in single-entry forms
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29711 Re: Snippet Generator: missing attribute names in single-entry forms Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy http://jenkins-ci.org/commit/docker-workflow-plugin/3ff3b8bfb06d722bc7f470ccf42b1016eb352fbb Log: May as well update a bit further and pick up the fix of JENKINS-29711 as well. 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-32731) Allow plugins to contribute to Pipeline global library
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32731 Re: Allow plugins to contribute to Pipeline global library Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/docker/workflow/DockerDSL.java src/main/java/org/jenkinsci/plugins/docker/workflow/ImageNameTokens.java src/main/resources/org/jenkinsci/plugins/docker/workflow/Docker.groovy http://jenkins-ci.org/commit/docker-workflow-plugin/223612bc8378cc3e02cc6fecee1416c5bd533af9 Log: Merge pull request #75 from jglick/GlobalVariable-JENKINS-32731 JENKINS-32731 JENKINS-34650 Docker.groovy is already trusted Compare: https://github.com/jenkinsci/docker-workflow-plugin/compare/1f5f9d0147c4...223612bc8378 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-32731) Allow plugins to contribute to Pipeline global library
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32731 Re: Allow plugins to contribute to Pipeline global library Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/docker/workflow/DockerDSL.java src/main/java/org/jenkinsci/plugins/docker/workflow/ImageNameTokens.java http://jenkins-ci.org/commit/docker-workflow-plugin/abe4066b6b4eb1af3e922897add192df4e0294ef Log: JENKINS-32731 JENKINS-34650 Docker.groovy is already trusted. 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-34650) Allow global libraries to bypass the sandbox
Title: Message Title SCM/JIRA link daemon commented on JENKINS-34650 Re: Allow global libraries to bypass the sandbox Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/docker/workflow/DockerDSL.java src/main/java/org/jenkinsci/plugins/docker/workflow/ImageNameTokens.java http://jenkins-ci.org/commit/docker-workflow-plugin/abe4066b6b4eb1af3e922897add192df4e0294ef Log: JENKINS-32731 JENKINS-34650 Docker.groovy is already trusted. 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-21079) Request to have the ability to stagger matrix builds by a certain amount of time
Title: Message Title hector CALDERON commented on JENKINS-21079 Re: Request to have the ability to stagger matrix builds by a certain amount of time Has there been any progress on this request? I am in the same situation, this addition would be helpful. 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-24805) Mask credentials in Build Log
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24805 Re: Mask credentials in Build Log Code changed in jenkins User: Andrew Bayer Path: src/main/java/org/jenkinsci/plugins/credentialsbinding/MultiBinding.java src/main/java/org/jenkinsci/plugins/credentialsbinding/impl/BindingStep.java src/main/java/org/jenkinsci/plugins/credentialsbinding/impl/SecretBuildWrapper.java http://jenkins-ci.org/commit/credentials-binding-plugin/a47f4b8529fd216c3c797566aa969191834abd7a Log: JENKINS-24805 First work on masking secrets in freestyle logs. This still needs tests - I just want to make sure the approach is right. 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-24805) Mask credentials in Build Log
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24805 Re: Mask credentials in Build Log Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/credentialsbinding/MultiBinding.java src/main/java/org/jenkinsci/plugins/credentialsbinding/impl/BindingStep.java src/main/java/org/jenkinsci/plugins/credentialsbinding/impl/SecretBuildWrapper.java src/test/java/org/jenkinsci/plugins/credentialsbinding/impl/SecretBuildWrapperTest.java http://jenkins-ci.org/commit/credentials-binding-plugin/d2bcf977eb334ee93774c94d8db1007afc5cad41 Log: Merge pull request #28 from abayer/jenkins-24805 JENKINS-24805 Start masking secrets in freestyle logs. Compare: https://github.com/jenkinsci/credentials-binding-plugin/compare/686a29f57bf7...d2bcf977eb33 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-24805) Mask credentials in Build Log
Title: Message Title Jesse Glick updated JENKINS-24805 Jenkins / JENKINS-24805 Mask credentials in Build Log Change By: Jesse Glick Status: In Review 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-30709) SCM env vars for multiple scm's plugin not useful with multiple git repos
Title: Message Title Ankit Maroo commented on JENKINS-30709 Re: SCM env vars for multiple scm's plugin not useful with multiple git repos Hi, we could access GIT_URL_N and GIT_COMMIT_N, etc variables before. seem like recent changes have broken it. Those variables arent available anymore. 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-31247) Copyartifact: more integration with workflow
Title: Message Title Ken Rachynski commented on JENKINS-31247 Re: Copyartifact: more integration with workflow I was just looking for this functionality in 1.38.1 and see that this request has been idle for just over a year. 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-32059) Workflow script echo back should have line number
Title: Message Title Jesse Glick commented on JENKINS-32059 Re: Workflow script echo back should have line number More generally, contrary to JENKINS-35308, there are missing line numbers in errors. For example, if a tool step fails buried deep in some library, you just see [Pipeline] End of Pipeline ERROR: No tool named … found Finished: FAILURE Even the ErrorAction in the workflow/*.xml corresponding to the FlowEndNode is not helpful here: "workflow-api@2.1"> "hudson.AbortException"> No tool named null found org.jenkinsci.plugins.workflow.steps.ToolStep$Execution.run(ToolStep.java:137) org.jenkinsci.plugins.workflow.steps.ToolStep$Execution.run(ToolStep.java:111) org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) hudson.security.ACL.impersonate(ACL.java:213) org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) java.lang.Thread.run(Thread.java:745) "java.util.Collections$UnmodifiableRandomAccessList" resolves-to="java.util.Collections$UnmodifiableList"> "list"/> "../c"/> Perhaps ErrorAction should include a second field encoding the stack trace of the StepExecution.start invocation, so we can track it back to a source line number. Or perhaps this could be added as a cause or suppressed exception in CpsStepContext.onFailure, so it appears automatically whenever printStackTrace is called, though this then breaks down when WorkflowRun.finish etc. handle AbortException specially. Another option is for every StepAtomNode/StepStartNode to encode a SourceLocation, which would enable the RFE originally requested here. Not clear to me how to get access to that location from DSL though. CpsThread.current().getStackTrace() perhaps? Add Comment
[JIRA] (JENKINS-35388) accurev-plugin parameters
Title: Message Title
Timothy Williams commented on JENKINS-35388
Re: accurev-plugin parameters
Thanks for the info! I was afraid you'd say that ("update"). I inherited this system from someone else, and let's just say that this system is very particular with what you do to it Thanks again.
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-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Ethan Vaughn commented on JENKINS-39332 Re: ApiSlRuntimeErrors.UnsafeCode error during analysis Could you please try to uncheck the second checkbox in the option menu and try to run again? Unchecked and still got the error. Did the first host (the one without the issue) was of the same version of LR? Yes. The original slave host was also running 12.02.0.0. 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-20139) add support to track where a credential is used
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20139 Re: add support to track where a credential is used Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/a69e1a5314a3d816273af697d8a0fabf59473f62 Log: JENKINS-20139 Inaccurate/incomplete Javadoc for `track` overloads. 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-30282) Jenkins Plugin HP Application Automation Tools provides no OSS License information.
Title: Message Title Yafim Kazak commented on JENKINS-30282 Re: Jenkins Plugin HP Application Automation Tools provides no OSS License information. Added. 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-20139) add support to track where a credential is used
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20139 Re: add support to track where a credential is used Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/d20ac24fde82efc58df1b0670374ce9718f7fd88 Log: Merge pull request #70 from jglick/track-Javadoc JENKINS-20139 Inaccurate/incomplete Javadoc for `track` overloads Compare: https://github.com/jenkinsci/credentials-plugin/compare/408765b9ad75...d20ac24fde82 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-34456) Image Gallery Plugin does not play nice with XML-Summary Report plugin
Title: Message Title John Gregg commented on JENKINS-34456 Re: Image Gallery Plugin does not play nice with XML-Summary Report plugin Not 100% sure my issue is the same, but I also use both of these plugins. They both use _javascript_. The Firefox debugger says "TypeError: jQuery(...).colorbox is not a function." In my case, the images do not appear on the build summary page. I can click into the build artifacts directory and see links to my images, however. thanks 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-29536) Remove restriction preventing non time based Loadrunner scenarios from running
Title: Message Title Yafim Kazak assigned an issue to Yafim Kazak Jenkins / JENKINS-29536 Remove restriction preventing non time based Loadrunner scenarios from running Change By: Yafim Kazak Assignee: Avishai Moshka Yafim Kazak 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-30282) Jenkins Plugin HP Application Automation Tools provides no OSS License information.
Title: Message Title Yafim Kazak closed an issue as Fixed Jenkins / JENKINS-30282 Jenkins Plugin HP Application Automation Tools provides no OSS License information. Change By: Yafim Kazak Status: Open Closed 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-39323) ArtifactoryPluginTest#gradle_integration test is failing
Title: Message Title Scott Hebert commented on JENKINS-39323 Re: ArtifactoryPluginTest#gradle_integration test is failing I am seeing this in my own test environment too. After some digging, the problem is coming from this: https://github.com/JFrogDev/build-info/commit/468139fd44cb124c41b2bdfda49ed5f0fc4e5c21 gradle.rootProject does not seem to have a method called "getPluginManager" Here is the stack trace from a run with the debug option: 16:24:26.366 [ERROR] [org.gradle.BuildExceptionReporter] org.gradle.api.internal.MissingMethodException: Could not find method getPluginManager() for arguments [] on root project 'YourNewName'. 16:24:26.366 [ERROR] [org.gradle.BuildExceptionReporter] at org.gradle.api.internal.AbstractDynamicObject.methodMissingException(AbstractDynamicObject.java:68) 16:24:26.366 [ERROR] [org.gradle.BuildExceptionReporter] at org.gradle.api.internal.AbstractDynamicObject.invokeMethod(AbstractDynamicObject.java:56) 16:24:26.367 [ERROR] [org.gradle.BuildExceptionReporter] at org.gradle.api.internal.CompositeDynamicObject.invokeMethod(CompositeDynamicObject.java:172) 16:24:26.367 [ERROR] [org.gradle.BuildExceptionReporter] at org.gradle.api.internal.project.DefaultProject_Decorated.invokeMethod(Unknown Source) 16:24:26.368 [ERROR] [org.gradle.BuildExceptionReporter] at org.jfrog.gradle.plugin.artifactory.extractor.listener.ProjectsEvaluatedBuildListener.projectsEvaluated(ProjectsEvaluatedBuildListener.groovy:51) ProjectsEvaluatedBuildListener.groovy seems to be part of build-info-extractor-gradle-4.4.5.jar Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you
[JIRA] (JENKINS-28075) Want to see the LoadRunner controller execute when runing from Jenkins
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-28075 Want to see the LoadRunner controller execute when runing from Jenkins Change By: Yafim Kazak Issue Type: Task Story 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-28075) Want to see the LoadRunner controller execute when runing from Jenkins
Title: Message Title Yafim Kazak commented on JENKINS-28075 Re: Want to see the LoadRunner controller execute when runing from Jenkins Will be added in our next releases as a 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-28075) Want to see the LoadRunner controller execute when runing from Jenkins
Title: Message Title Yafim Kazak updated an issue Jenkins / JENKINS-28075 Want to see the LoadRunner controller execute when runing from Jenkins Change By: Yafim Kazak Issue Type: Bug Task 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-39376) Constant StackOverflowError when building pipeline jobs
Title: Message Title Jesse Glick resolved as Incomplete 2.4 might be a version number of some plugin, but not all of them. And there is no stack trace shown here. Jenkins / JENKINS-39376 Constant StackOverflowError when building pipeline jobs Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete 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
[JIRA] (JENKINS-38171) Project Recognizer for Jenkinsfile in another repository.
Title: Message Title Joshua Kegley commented on JENKINS-38171 Re: Project Recognizer for Jenkinsfile in another repository. I'd like to also know where this. I want to support JSON or other file formats. 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-26700) Download build artifacts as zip generates a corrupted file
Title: Message Title Srinivasan Venkataraman edited a comment on JENKINS-26700 Re: Download build artifacts as zip generates a corrupted file I am facing the same issue. We are on Jenkins ver. 2.19.1We have a powershell script downloading a build artifact zip. The zip is much smaller when the download is complete.Invoke-WebRequest -URI $jenkinsLink/$majorVersion.$minorVersion/ws/$fileToDownload -ErrorAction:Stop -TimeoutSec 300 -OutFile $fileToDownload Downloaded zip is unusable, not a valid archive. This is a critical issue and breaks the chain in our CI/Dev Ops. This is the exception we have in the logs Caught exception evaluating: request.getSession() in /job/2016.2/ws/PrintStreamUpdate_2016.2.818.0.zip. Reason: java.lang.IllegalStateException: Response is committedjava.lang.IllegalStateException: Response is committed at org.eclipse.jetty.server.Request.getSession(Request.java:1400) at org.eclipse.jetty.server.Request.getSession(Request.java:1378) at javax.servlet.http.HttpServletRequestWrapper.getSession(HttpServletRequestWrapper.java:279) at sun.reflect.GeneratedMethodAccessor243.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:95) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at hudson.init.impl.InstallUncaughtExceptionHandler$1.reportException(InstallUncaughtExceptionHandler.java:30) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:52) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585) at
[JIRA] (JENKINS-39275) DurableTaskStep$Execution.getStatus can hang
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39275 Re: DurableTaskStep$Execution.getStatus can hang Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDump.java http://jenkins-ci.org/commit/workflow-cps-plugin/8803767e994f24d8606c80ace97f7468deaaf34d Log: Merge pull request #81 from jglick/getStatus-JENKINS-39275 JENKINS-39275 Extend time limit to virtual thread dump Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/4c00f9988826...8803767e994f 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-39275) DurableTaskStep$Execution.getStatus can hang
Title: Message Title Jesse Glick updated JENKINS-39275 Jenkins / JENKINS-39275 DurableTaskStep$Execution.getStatus can hang Change By: Jesse Glick Status: In Review 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-39275) DurableTaskStep$Execution.getStatus can hang
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39275 Re: DurableTaskStep$Execution.getStatus can hang Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadDump.java http://jenkins-ci.org/commit/workflow-cps-plugin/a08717eaea66e211a6d0e01bbf171b814f8bf96c Log: JENKINS-39275 Extend time limit to virtual thread dump. 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-26700) Download build artifacts as zip generates a corrupted file
Title: Message Title Srinivasan Venkataraman commented on JENKINS-26700 Re: Download build artifacts as zip generates a corrupted file I am facing the same issue. We are on Jenkins ver. 2.19.1 We have a powershell script downloading a build artifact zip. The zip is much smaller when the download is complete. Invoke-WebRequest -URI $jenkinsLink/$majorVersion.$minorVersion/ws/$fileToDownload -ErrorAction:Stop -TimeoutSec 300 -OutFile $fileToDownload Downloaded zip is unusable, not a valid archive. This is a critical issue and breaks the chain in our CI/Dev Ops. 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-39390) Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread
Title: Message Title Jesse Glick resolved as Cannot Reproduce Looks like your Jenkins installation is somehow broken but I can hardly guess how. The quoted exception detail message does not look like it is even a possible message from JRE, since it is giving a (binary) class name, not a method name. Try reinstalling. Jenkins / JENKINS-39390 Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You
[JIRA] (JENKINS-39390) Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-39390 Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread Change By: Jesse Glick Assignee: Jesse Glick 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-39391) Support for from index greater than the actual array size during pagination
Title: Message Title
Pratith Kanagaraj updated an issue
Jenkins / JENKINS-39391
Support for from index greater than the actual array size during pagination
Change By:
Pratith Kanagaraj
In range notation during pagination, if the from index exceeds the actual array size, Jenkins throws an exception. Can't it return an empty response or something similar instead , so that we know when to stop ?For example, suppose a Jenkins server has 10840 jobs and we want to get all the jobs' details. We keep incrementing the lower bound according to page size (say 1000). Eventually, we hit: http://server/api/json?tree=jobs[name,url,builds[number,url]]{11000,12000} which throws the following exception:Caused by: java.lang.IllegalArgumentException: fromIndex(11000) > toIndex(10841)
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
[JIRA] (JENKINS-39391) Support for from index greater than the actual array size during pagination
Title: Message Title
Pratith Kanagaraj created an issue
Jenkins / JENKINS-39391
Support for from index greater than the actual array size during pagination
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2016/Oct/31 7:54 PM
Priority:
Major
Reporter:
Pratith Kanagaraj
In range notation during pagination, if the from index exceeds the actual array size, Jenkins throws an exception. Can't it return an empty response or something similar instead? For example, suppose a Jenkins server has 10840 jobs and we want to get all the jobs' details. We keep incrementing the lower bound according to page size (say 1000). Eventually, we hit: http://server/api/json?tree=jobs[name,url,builds[number,url]] {11000,12000} which throws the following exception: Caused by: java.lang.IllegalArgumentException: fromIndex(11000) > toIndex(10841)
Add Comment
[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak edited a comment on JENKINS-39332 Re: ApiSlRuntimeErrors.UnsafeCode error during analysis * Could you please try to uncheck the second checkbox in the option menu and try to run again? It's not necessary when running using Jenkins - since the plugin tries to create new directory regardless of this option.* It seems as the major issue is the report template missing HTML default format.* Did the first host (the one without the issue) was of the same version of LR?I will try to reproduce it on the same LR version you have ( the plugin is constantly tested on the latest versions of LR) to see if it's LR 12.02 specific issue or a plugin 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-39390) Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread
Title: Message Title Smithesh Purushothaman commented on JENKINS-39390 Re: Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread Jesse Glick - Can you shed some light on the above issue. This put me in dark without any clue what to do next. Please help 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-39390) Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread
Title: Message Title Smithesh Purushothaman assigned an issue to Jesse Glick Jenkins / JENKINS-39390 Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread Change By: Smithesh Purushothaman Assignee: Jesse Glick 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-39390) Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread
Title: Message Title Smithesh Purushothaman created an issue Jenkins / JENKINS-39390 Pipeline Job unable to execute java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2016/Oct/31 7:43 PM Priority: Minor Reporter: Smithesh Purushothaman Pipeline job is unable to execute and failed with below error java.lang.NoSuchMethodError: org/jenkinsci/plugins/workflow/cps/CpsThread at org.jenkinsci.plugins.workflow.cps.CpsScript.(CpsScript.java:69) at WorkflowScript.(WorkflowScript) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance0(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.codehaus.groovy.runtime.InvokerHelper.createScript(InvokerHelper.java:432) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:411) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:374) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:220) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: FAILURE
[JIRA] (JENKINS-39389) Add an implementation of jenkins.scm.api.SCMSource
Title: Message Title Martin Weber created an issue Jenkins / JENKINS-39389 Add an implementation of jenkins.scm.api.SCMSource Issue Type: New Feature Assignee: Kevin Bell Components: multiple-scms-plugin Created: 2016/Oct/31 7:19 PM Priority: Trivial Reporter: Martin Weber Please, add an implementation of jenkins.scm.api.SCMSource to make MultiSCM available in multi-branch-project-plugin. This would be helpful, since multi-branch-project-plugin allows to monitor multiple SCMs already but copies only the first SCM to the created sub-project. Add Comment
[JIRA] (JENKINS-39332) ApiSlRuntimeErrors.UnsafeCode error during analysis
Title: Message Title Yafim Kazak commented on JENKINS-39332 Re: ApiSlRuntimeErrors.UnsafeCode error during analysis Could you please try to uncheck the second checkbox in the option menu and try to run again? It's not necessary when running using Jenkins - since the plugin tries to create new directory regardless of this option. It seems as the major issue is the report template missing HTML default format. Did the first host (the one without the issue) was of the same version of LR? I will try to reproduce it on the same LR version you have ( the plugin is constantly tested on the latest versions of LR) to see if it's LR 12.02 specific issue or a plugin 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-39388) Sporadic Jenkins Crashing Across Different Servers
Title: Message Title Corey Carvalho updated an issue Jenkins / JENKINS-39388 Sporadic Jenkins Crashing Across Different Servers Change By: Corey Carvalho We are experiencing an issue with our Jenkins servers (multiple) crashing sporadically throughout the day. Initially, there was thought that it could be a JDK version issue and went through with updating the JDK on our servers, however this did not solve the issue. Attached are the following four log files produced by the jvm: - log1.txt and log2.txt are before the JDK update from two of our servers - hs_err.txt (Jenkins v. 1.651.1) and hs_err2.txt (Jenkins v. 1.580.3) are after the JDK update from two of our servers 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-39388) Sporadic Jenkins Crashing Across Different Servers
Title: Message Title Corey Carvalho created an issue Jenkins / JENKINS-39388 Sporadic Jenkins Crashing Across Different Servers Issue Type: Bug Assignee: Unassigned Attachments: hs_err.txt, hs_err2.txt, log1.txt, log2.txt Components: core Created: 2016/Oct/31 7:14 PM Priority: Critical Reporter: Corey Carvalho We are experiencing an issue with our Jenkins servers crashing sporadically throughout the day. Initially, there was thought that it could be a JDK version issue and went through with updating the JDK on our servers, however this did not solve the issue. Attached are the following four log files produced by the jvm: log1.txt and log2.txt are before the JDK update from two of our servers hs_err.txt (Jenkins v. 1.651.1) and hs_err2.txt (Jenkins v. 1.580.3) are after the JDK update from two of our servers
[JIRA] (JENKINS-24805) Mask credentials in Build Log
Title: Message Title Andrew Bayer updated JENKINS-24805 Jenkins / JENKINS-24805 Mask credentials in Build Log Change By: Andrew Bayer Status: In Progress Review 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-24805) Mask credentials in Build Log
Title: Message Title Andrew Bayer commented on JENKINS-24805 Re: Mask credentials in Build Log One more attempt at a PR up for review - https://github.com/jenkinsci/credentials-binding-plugin/pull/28 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-33619) Script definition area rendered over header section
Title: Message Title Jesse Glick commented on JENKINS-33619 Re: Script definition area rendered over header section If you cannot reproduce then best just to close I guess. 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-33703) Exceptions in generated DSL documentation for `unarchive`
Title: Message Title Jesse Glick commented on JENKINS-33703 Re: Exceptions in generated DSL documentation for `unarchive` No, it is a waste of time since ArtifactUnarchiverStep/config.jelly does not even try to support visual configuration. Should just move that blurb into help.html and make the f:block say to look at it (so that the static reference shows docs for the step); and make html.groovy quietly skip over the mappings attribute somehow, without showing the ugly exception. 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-33703) Exceptions in generated DSL documentation for `unarchive`
Title: Message Title Jesse Glick assigned an issue to Andrew Bayer Jenkins / JENKINS-33703 Exceptions in generated DSL documentation for `unarchive` Change By: Jesse Glick Assignee: CloudBees Inc. Andrew Bayer 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-35370) Workflow shell step ERROR: script returned exit code -1
Title: Message Title Jesse Glick commented on JENKINS-35370 Re: Workflow shell step ERROR: script returned exit code -1 Typically it means workspace sharing between host & container is failing. If the agent itself is inside a container, make sure --volumes-from is included on the command line; if not, nothing will 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-30019) Next Build Number plugin does not work with Jenkins Workflow jobs
Title: Message Title Jesse Glick commented on JENKINS-30019 Re: Next Build Number plugin does not work with Jenkins Workflow jobs A user list question, best kept out of JIRA. 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-39275) DurableTaskStep$Execution.getStatus can hang
Title: Message Title Jesse Glick updated JENKINS-39275 Jenkins / JENKINS-39275 DurableTaskStep$Execution.getStatus can hang Change By: Jesse Glick Status: In Progress Review 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-30019) Next Build Number plugin does not work with Jenkins Workflow jobs
Title: Message Title
Swati Jain commented on JENKINS-30019
Re: Next Build Number plugin does not work with Jenkins Workflow jobs
Jesse GlickI tried setting up next build number in multi branch pipeline for my release build through script but it is not working. Below is the code which I tried def job = Jenkins.instance.getItem("master") job.nextBuildNumber = env.BUILD_NUMBER + 1 job.saveNextBuildNumber() I tried using CLI command also "java -jar $ {env.HOME} jenkins-cli.jar -s XX-JENKINS-SERVER" set-next-build-number 'Pipeline/master' 44" but nothing seems to work for pipeline job. As compatibility issue is addressed here please guide me how I can do that. I understand you guys don't recommend it but it is our requirement.TIA
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-39275) DurableTaskStep$Execution.getStatus can hang
Title: Message Title Jesse Glick started work on JENKINS-39275 Change By: Jesse Glick Status: Open In Progress 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-39275) DurableTaskStep$Execution.getStatus can hang
Title: Message Title Jesse Glick commented on JENKINS-39275 Re: DurableTaskStep$Execution.getStatus can hang Note that the stack trace quoted above should only happen if you have enabled a FINE logger. 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-35370) Workflow shell step ERROR: script returned exit code -1
Title: Message Title Ben Mathews commented on JENKINS-35370 Re: Workflow shell step ERROR: script returned exit code -1 I'm seeing a similar issue where the sh command inside a docker.image block always terminates after some delay. The point in the sh command that jenkins errors out varies which leads me to believe that jenkins is causing the problem. I'm on the latest version of jenkins and all plugins. Any tips on how to debug 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-24805) Mask credentials in Build Log
Title: Message Title Jesse Glick assigned an issue to Andrew Bayer Jenkins / JENKINS-24805 Mask credentials in Build Log Change By: Jesse Glick Assignee: Paul Idstein Andrew Bayer 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-39334) Unable to run script.sh using "Execute shell script on remote host using ssh"
Title: Message Title Jimmy Vo commented on JENKINS-39334 Re: Unable to run script.sh using "Execute shell script on remote host using ssh" Sorry, I put in the wrong order of "-ex" last time. This time I put in the right order of "-ex" in the command and test it, but it still doesn't give any information of execution in the Console Output. It just shows it is running with a spining icon and it runs forever: "Building remotely on Px-Winchill_NCR2.0Nov (Px_Winchill) in workspace /temp/workspace/Test executing script: sh -ex /Path-To-File/cbif/setup.sh -Dcbif.install.zip=/Path-To-File/patch.zip -Dcbif.install.quiet=true -Dcbif.install.noRestart=true -Dcbif.install.phaseTwoOnly=true -Dcbif.install.force=true " Thank you 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.
