[JIRA] (JENKINS-37463) Link to the job out of Blue Ocean/pipeline stage view
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37463 Link to the job out of Blue Ocean/pipeline stage view Change By: Sam Van Oort Summary: Link to the job out of Blue Ocean/ pipeline stage view 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-37463) Link to the job out of pipeline stage view
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37463 Link to the job out of pipeline stage view Change By: Sam Van Oort Component/s: blueocean-plugin 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-37463) Link to the job out of pipeline stage view
Title: Message Title Sam Van Oort resolved as Won't Fix Argh, never mind, that was a different but similar JIRA I meant to tag. Jenkins / JENKINS-37463 Link to the job out of pipeline stage view Change By: Sam Van Oort 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
[JIRA] (JENKINS-37463) Link to the job out of Blue Ocean/pipeline stage view
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-37463 Link to the job out of Blue Ocean/pipeline stage view Change By: Sam Van Oort Component/s: pipeline-stage-view-plugin Component/s: blueocean-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-37463) Link to the job out of Blue Ocean/pipeline stage view
Title: Message Title Sam Van Oort updated JENKINS-37463 Jenkins / JENKINS-37463 Link to the job out of Blue Ocean/pipeline stage view Change By: Sam Van Oort Status: Reopened 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-37463) Link to the job out of pipeline stage view
Title: Message Title Sam Van Oort reopened an issue Re-opening because this should probably be a backlog RFE for Blue Ocean's rather than totally closed Jenkins / JENKINS-37463 Link to the job out of pipeline stage view Change By: Sam Van Oort Resolution: Won't Fix 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 jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-35656) Inconsistent timezone display
Title: Message Title Sam Van Oort started work on JENKINS-35656 Change By: Sam Van Oort 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-37934) NTLM Authentication No Matter What
Title: Message Title Olivier Dagenais commented on JENKINS-37934 Re: NTLM Authentication No Matter What Mark Waite: The TFS plugin doesn't do too much with the git-client-plugin; there's a dependency on git-plugin to be able to subclass RevisionParameterAction to be able to ask for a specific commit to be built, as well as pass around some extra data and be able to more loosely match repository URLs. I am hoping you will see, via my testing in pull request #216, that you can take tfs-plugin out of the equation. Joshua Barton: The above pull request might be relevant to your interests... 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-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Pragya Jaiswal edited a comment on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Thanks Mark. that does resolve my issue. However, how can I extend the functionality of my jenkins job -My jenkins job tracks multiple branches and triggers builds if there are changes to any of those branches. For example I have multiple branch specifiers added to my job -origin/release**origin/developThe job is working fine when there are merges to any of these branches.In some cases I want to be able to specify/input a branch to pull the source and build from. How can I accomplish that considering I have the branch specifiers already set? Any ideas on implementing this?I tried a couple of things -1. Added a build parameters called $BranchOverride and tried 2 test cases. case 1 - Setting the default value to "None" with 3 branch specifiers for release/*, develop and $BranchOverride. Case 2 - setting the default value to origin/develop and set 2 branch specifiers release/* and $BranchOverride. Both the cases, when I manually input a branch, it doesn't work as I expect it to.2. Instead of specifying multiple Branch specifiers, I created a string Parameter $BranchOverride and set the value as a regex :(?=(origin/develop|origin/release)).*When I push to one of my release branch, it triggers a build (and multiple consecutive builds) for multiple branches, even those that dont have any push. I see this is the log -Seen 1,116 remote branchesMultiple candidate revisionsScheduling another build to catch up with ABC_TestJobChecking out Revision 366bdc3674103e4b2479d75508f3971c6f080591 (origin/release/xyz)Maybe I am not understanding the behavior correctly, am not sure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33984) Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1)
Title: Message Title Pragya Jaiswal commented on JENKINS-33984 Re: Git plugin sets wrong branch name GIT_BRANCH (more than 2 branches with same SHA1) Thanks Mark. that does resolve my issue. However, how can I extend the functionality of my jenkins job - My jenkins job tracks multiple branches and triggers builds if there are changes to any of those branches. For example I have multiple branch specifiers added to my job - origin/release** origin/develop The job is working fine when there are merges to any of these branches.In some cases I want to be able to specify/input a branch to pull the source and build from. How can I accomplish that considering I have the branch specifiers already set? Any ideas on implementing this? I tried a couple of things - 1. Added a build parameters called $BranchOverride and tried 2 test cases. case 1 - Setting the default value to "None" with 3 branch specifiers for release/, develop and $BranchOverride. Case 2 - setting the default value to origin/develop and set 2 branch specifiers release/ and $BranchOverride. Both the cases, when I manually input a branch, it doesn't work as I expect it to. 2. Instead of specifying multiple Branch specifiers, I created a string Parameter $BranchOverride and set the value as a regex ?=(origin/develop|origin/release)).* When I push to one of my release branch, it triggers a build (and multiple consecutive builds) for multiple branches, even those that dont have any push. I see this is the log - Seen 1,116 remote branches Multiple candidate revisions Scheduling another build to catch up with ABC_TestJob Checking out Revision 366bdc3674103e4b2479d75508f3971c6f080591 (origin/release/xyz) Maybe I am not understanding the behavior correctly, am not sure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Sam Van Oort commented on JENKINS-26522
Re: Annotated block/stage status
Alex Dean There's a variety of different ways to use it, I think. The simplest ones:
// Annotations are string-string key:value pairs now
stage('example') {
annotate('WebLink','http://example.com');
annotate('MySpecialCondition','true');
}
Possibly we might want to allow it to take blocks?
// Annotations are string-string key:value pairs now
stage('example') {
annotate('WebLink','http://example.com') {
sh './deploy.sh www.example.com'
}
}
Also, we could use it for status-overrides, if simple support is added to the pipeline-graph-analysis plugin:
// Annotations are string-string key:value pairs now
stage('example') {
try {
sh 'mvn flakyTest'
} catch (Exception ex) {
stageStatus 'UNSTABLE'; // Sets *just this* stage status to unstable (once status computation supports it) without changing the overall build result.
annotate('currentStage.status', 'UNSTABLE'); // actually creates the same result?
}
}
Or at least that's what would make sense to me, not sure what others think.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-37253) only "Build origin branches also filed as PRs" not working
Title: Message Title Jesse Glick updated JENKINS-37253 Jenkins / JENKINS-37253 only "Build origin branches also filed as PRs" not working 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-38332) Input steps to set their result as an environment variable
Title: Message Title Patrick Wolf updated an issue Jenkins / JENKINS-38332 Input steps to set their result as an environment variable Change By: Patrick Wolf Component/s: pipeline-input-step-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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater commented on JENKINS-38210 Re: Can't link to blue ocean jobs inside folders I have uploaded job_in_folder.gif. Yeah my steps are so simple that I wonder if it's something going on with our corporate network. What you don't see off screen in the gif is that I switch to blue ocean UI after building the vanilla job. Then when I get to list view showing the completed job I highlight the URL in address bar and press enter and everything goes white. 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-38210) Can't link to blue ocean jobs inside folders
Title: Message Title Justin Rainwater updated an issue Jenkins / JENKINS-38210 Can't link to blue ocean jobs inside folders Change By: Justin Rainwater Attachment: job_in_folder.gif 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-38353) Add support for multi-branch pipeline
Title: Message Title Bryan Hunt created an issue Jenkins / JENKINS-38353 Add support for multi-branch pipeline Issue Type: New Feature Assignee: Oleg Nenashev Components: ownership-plugin Created: 2016/Sep/19 6:05 PM Priority: Major Reporter: Bryan Hunt We need the ability to assign ownership to a multi-branch pipeline project and have that ownership be propagated to any child jobs automatically created by Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38332) Input steps to set their result as an environment variable
Title: Message Title Andrew Bayer commented on JENKINS-38332 Re: Input steps to set their result as an environment variable Which means solving it in the input step, since we'll get whatever benefits from that for free elsewhere. 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-38338) Opening Robot Framework report failes
Title: Message Title selur vedu closed an issue as Duplicate Resolving as duplicate of the more popular issue JENKINS-32118 which contains a workaround/solution. Jenkins / JENKINS-38338 Opening Robot Framework report failes Change By: selur vedu Status: Open Closed 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
[JIRA] (JENKINS-38332) Input steps to set their result as an environment variable
Title: Message Title Patrick Wolf commented on JENKINS-38332 Re: Input steps to set their result as an environment variable This is a problem in both Declarative Pipeline and Pipeline Script. We need to solve the underlying problem for both 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-22660) More flexible UI for approved signatures
Title: Message Title Jesse Glick commented on JENKINS-22660 Re: More flexible UI for approved signatures Currently requires manual editing of $JENKINS_HOME/scriptApproval.xml. 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-38352) allow script aprovals to be removed individually, instead of erasing all of them
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-38352 allow script aprovals to be removed individually, instead of erasing all of them Change By: Jesse Glick Status: Open 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-38352) allow script aprovals to be removed individually, instead of erasing all of them
Title: Message Title Jesse Glick commented on JENKINS-38352 Re: allow script aprovals to be removed individually, instead of erasing all of them Added a blacklist entry. 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-38352) allow script aprovals to be removed individually, instead of erasing all of them
Title: Message Title Leah Klearman created an issue Jenkins / JENKINS-38352 allow script aprovals to be removed individually, instead of erasing all of them Issue Type: Improvement Assignee: Jesse Glick Components: script-security-plugin Created: 2016/Sep/19 5:50 PM Environment: 2.x Priority: Minor Reporter: Leah Klearman oops, i added an approval for System.exit() before i learned that it causes the entire JVM to close. it would really make sense for me to delete the approval, but i don't want to loose every other approval i've created. if such a thing exists as a script blacklist, it might make sense to put System.exit() on it. Add Comment
[JIRA] (JENKINS-26522) Annotated block/stage status
Title: Message Title
Alex Dean edited a comment on JENKINS-26522
Re: Annotated block/stage status
[~svanoort] could you provide a brief example of how this will be used in a Jenkins file? From your description I'm imagining something like this, but I'm not sure if I've understood correctly or not. ``` {code} node { stage('example') {if (condition) { note('condition was true')} else { note('condition was false')} }} ``` {code} and then the "condition was (true|false)" notation would be reported in the project's stage view?
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-26522) Annotated block/stage status
Title: Message Title
Alex Dean commented on JENKINS-26522
Re: Annotated block/stage status
Sam Van Oort could you provide a brief example of how this will be used in a Jenkins file? From your description I'm imagining something like this, but I'm not sure if I've understood correctly or not. ``` node { stage('example') { if (condition) { note('condition was true') } else { note('condition was false') } } } ``` and then the "condition was (true|false)" notation would be reported in the project's stage view?
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-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38152 Re: Jenkinsfile schema Java API as WorkflowRun action Code changed in jenkins User: Andrew Bayer Path: EXTENDING.md src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/Utils.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTAgent.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTBranch.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTBuildCondition.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTElement.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTEnvironment.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTNamedArgumentList.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTNotifications.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPipelineDef.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPositionalArgumentList.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTPostBuild.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTSingleArgument.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStages.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStep.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTTools.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTTreeStep.groovy src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/Converter.groovy src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/actions/ExecutionModelAction.java src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ModelConverterAction.java src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/ErrorsEndpointOpsTest.java src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/endpoints/SuccessfulEndpointOpsTest.java src/test/resources/executionModelAction.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/b385ba5d5015504e91ba9e297283282bd4ce94a5 Log: Merge pull request #14 from abayer/jenkins-38152 JENKINS-38152 - expose execution model on WorkflowRun Compare: https://github.com/jenkinsci/pipeline-model-definition-plugin/compare/7ae4f284c762...b385ba5d5015 Add Comment
[JIRA] (JENKINS-26522) Annotated block/stage status
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26522 Re: Annotated block/stage status Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/actions/TagsAction.java http://jenkins-ci.org/commit/workflow-api-plugin/43f7e86b0323d7031429b5e5552393eb9d027bfe Log: Merge pull request #14 from jenkinsci/revert-12-tagsaction-JENKINS-26522 Revert "Create a new TagsAction JENKINS-26522" Compare: https://github.com/jenkinsci/workflow-api-plugin/compare/f6de209ae708...43f7e86b0323 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-36210) expose details through REST API
Title: Message Title Larry Cai commented on JENKINS-36210 Re: expose details through REST API First thought is the url like you stated "/view//api/json?pretty=true=3". And if it is not possible, you can decide the suitable url to use. Surely I hope the url can contain the view name. Thanks. Rgs, Larry 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-38223) Incorrect state of completed parallel branch
Title: Message Title Vivek Pandey commented on JENKINS-38223 Re: Incorrect state of completed parallel branch Jesse Glick >but I can see no way that could ever have been implemented, since the BlockEndNode for parallel is not constructed until after all branches have completed. So I guess the Javadoc needs to be edited to stop making that claim. Hmm, thats the bug, I have BlockEndNode for that parallel branch, very fact that its been already constructed then it should be returning false for isRunning(), no? I am not calling isRunning() on a step inside parallel branch, its on the BlockEndNode of that branch. >The use case you cite makes no sense. If the branch has a BlockEndNode, then by definition it has completed. Rather than asking caller to infer that all has ended since you have this end block, which is true but 'isRunning() API' makes no sense to return true in this case 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-38152) Jenkinsfile schema Java API as WorkflowRun action
Title: Message Title Andrew Bayer resolved as Fixed Jenkins / JENKINS-38152 Jenkinsfile schema Java API as WorkflowRun action Change By: Andrew Bayer 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-28881) Add support for CloudBees folder plugin
Title: Message Title Oleg Nenashev commented on JENKINS-28881 Re: Add support for CloudBees folder plugin Bryan Hunt Multi-branch parent configurations are not folders, hence it is unlikely related. Could you please create a new issue for it? Likely I will need to create extension point and implement it in Multibranch 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-38223) Incorrect state of completed parallel branch
Title: Message Title Jesse Glick commented on JENKINS-38223 Re: Incorrect state of completed parallel branch Javadoc does claim be false for something that has finished but is pending child node creation, such as a completed fork branch which is waiting for the join node to be created but I can see no way that could ever have been implemented, since the BlockEndNode for parallel is not constructed until after all branches have completed. So I guess the Javadoc needs to be edited to stop making that claim. The use case you cite makes no sense. If the branch has a BlockEndNode, then by definition it has completed. 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-38335) Search API too slow for dashboard
Title: Message Title Vivek Pandey started work on JENKINS-38335 Change By: Vivek Pandey 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-38350) Unable to build Android app getting Could not expand ZIP error
Title: Message Title Christopher Orr closed an issue as Not A Defect The Gradle part of your build is failing, so this doesn't look like an issue with any of the various plugins to which you assigned this issue. It also sounds like you upgraded a bunch of different things at the same time. You need to figure out which version of Jenkins worked before with your current project setup, and then which is the first version of Jenkins where the exact same project setup does not work. If you have that info, and it looks like a relevant bug (e.g. in the Gradle plugin, or in Jenkins core), then you can open an issue with that information. Jenkins / JENKINS-38350 Unable to build Android app getting Could not expand ZIP error Change By: Christopher Orr Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38331) per stage agent directives
Title: Message Title Patrick Wolf commented on JENKINS-38331 Re: per stage agent directives btw, we should probably also flag things like "input inside a node" as part of our pre-compilation syntax checking. 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-38351) Add job DSL script support for aws device farm plugin
Title: Message Title Sanyasirao Mopada created an issue Jenkins / JENKINS-38351 Add job DSL script support for aws device farm plugin Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Sep/19 4:59 PM Priority: Blocker Reporter: Sanyasirao Mopada I'm unable to find script to configure aws device farm plugin job-dsl groovy script? I spent time to search them. I'm unable to find. Am I missing something? If not please add support for it Add Comment This
[JIRA] (JENKINS-38349) Add DSL support for Google Play Android Publisher Plugin
Title: Message Title Sanyasirao Mopada updated an issue Jenkins / JENKINS-38349 Add DSL support for Google Play Android Publisher Plugin Change By: Sanyasirao Mopada Priority: Minor Blocker 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-38350) Unable to build Android app getting Could not expand ZIP error
Title: Message Title Derrik Ammons updated an issue Jenkins / JENKINS-38350 Unable to build Android app getting Could not expand ZIP error Change By: Derrik Ammons We decided to support Android 7.0 (API 24) for our Android App and upgraded our Gradle 2.10 to 2.14.1 and JDK7 to JDK8u102. We are unable to build our app in Jenkins 2.22 and 2.23 releases. We are getting a Could not expand ZIP error that we didn't get before. And I am able to build it successfully, both debug and release variants, in Android Studio using the same JDK8u102 and Gradle 2.14.1 on both Windows and Mac.I attached the the stacktrace. Let me know what other info you need. 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-38350) Unable to build Android app getting Could not expand ZIP error
Title: Message Title Derrik Ammons created an issue Jenkins / JENKINS-38350 Unable to build Android app getting Could not expand ZIP error Issue Type: Bug Assignee: Christopher Orr Attachments: exception.txt Components: android-emulator-plugin, android-lint-plugin, bitbucket-plugin, bitbucket-pullrequest-builder-plugin Created: 2016/Sep/19 4:56 PM Environment: Jenkins 2.22 and 2.23 on Windows. Priority: Major Reporter: Derrik Ammons We decided to support Android 7.0 (API 24) for our Android App and upgraded our Gradle 2.10 to 2.14.1 and JDK7 to JDK8u102. We are unable to build our app in Jenkins 2.22 and 2.23 releases. We are getting a Could not expand ZIP error that we didn't get before. And I am able to build it successfully, both debug and release variants, in Android Studio using the same JDK8u102 and Gradle 2.14.1 on both Windows and Mac. I attached the the stacktrace.
[JIRA] (JENKINS-38349) Add DSL support for Google Play Android Publisher Plugin
Title: Message Title Sanyasirao Mopada commented on JENKINS-38349 Re: Add DSL support for Google Play Android Publisher Plugin Sorry for that, This is my first issue. I don't know about that. 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-26522) Annotated block/stage status
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26522 Re: Annotated block/stage status Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/actions/TagsAction.java http://jenkins-ci.org/commit/workflow-api-plugin/428319414b7fa7288bec1652202188a1ea52daa5 Log: Revert "Create a new TagsAction 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-38349) Add DSL support for Google Play Android Publisher Plugin
Title: Message Title Christopher Orr assigned an issue to Daniel Spilker Jenkins / JENKINS-38349 Add DSL support for Google Play Android Publisher Plugin Change By: Christopher Orr Assignee: Christopher Orr Daniel Spilker 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-38349) Add DSL support for Google Play Android Publisher Plugin
Title: Message Title Christopher Orr commented on JENKINS-38349 Re: Add DSL support for Google Play Android Publisher Plugin Please don't set multiple plugin components; and if you're looking for DSL support for multiple plugins, it would be best to file separate tickets. 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-38349) Add DSL support for Google Play Android Publisher Plugin
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-38349 Add DSL support for Google Play Android Publisher Plugin Change By: Christopher Orr Summary: add Add DSL support for dsl script for aws device farm plugin, google play android publisher plugin configurations? Google Play Android Publisher 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-38349) add support for dsl script for aws device farm plugin, google play android publisher plugin configurations?
Title: Message Title Christopher Orr updated an issue Jenkins / JENKINS-38349 add support for dsl script for aws device farm plugin, google play android publisher plugin configurations? Change By: Christopher Orr Component/s: google-play-android-publisher-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-38349) add support for dsl script for aws device farm plugin, google play android publisher plugin configurations?
Title: Message Title Sanyasirao Mopada created an issue Jenkins / JENKINS-38349 add support for dsl script for aws device farm plugin, google play android publisher plugin configurations? Issue Type: Improvement Assignee: Christopher Orr Components: google-play-android-publisher-plugin, job-dsl-plugin Created: 2016/Sep/19 4:46 PM Priority: Minor Reporter: Sanyasirao Mopada I'm unable to find script to configure aws device farm plugin , google play services using job-dsl groovy script? I spent time to search them. I'm unable to find. Am I missing something? If not please add support for it Add Comment
[JIRA] (JENKINS-26522) Annotated block/stage status
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26522 Re: Annotated block/stage status Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/actions/TagsAction.java http://jenkins-ci.org/commit/workflow-api-plugin/f6de209ae70887dd47a28075f1972bf1642b68d7 Log: Merge pull request #12 from jenkinsci/tagsaction-JENKINS-26522 Create a new TagsAction JENKINS-26522 Compare: https://github.com/jenkinsci/workflow-api-plugin/compare/8ca82ae8180d...f6de209ae708 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-37359) Support private GitHub repositories in multibranch projects
Title: Message Title Jesse Glick resolved as Cannot Reproduce The pulldown does take into account credentials to list private repositories. It can take a while, pending GraphQL integration, so if you have typed the organization name first then Jenkins will start to populate the list using the initially selected anonymous access, and later come back and revise the list with the actual access token. Jenkins / JENKINS-37359 Support private GitHub repositories in multibranch projects 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)
[JIRA] (JENKINS-37987) Image.inside fails for images specifying ENTRYPOINT
Title: Message Title Logan Glickfield commented on JENKINS-37987 Re: Image.inside fails for images specifying ENTRYPOINT Jesse Glick: I agree with David LaBissoniere and am having trouble using any image now that specifies an ENTRYPOINT in the dockerfile. 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-38331) per stage agent directives
Title: Message Title
Patrick Wolf commented on JENKINS-38331
Re: per stage agent directives
Michael Neale I assumed it was a typo. Just pointing it out for anyone else reading. There were a few things. First, at a bare minimum we need per-stage agent directives when agent none is used but we should also allow per-stage directives that override any global agent.
pipeline{
agent docker:"ubuntu"
stages{
stage("Foo"){
agent none
echo "Foo"
}
stage("Bar"){
echo "Bar"
}
}
}
and
pipeline{ agent none stages{ stage("Foo") { echo "Foo" } stage("Bar") { agent docker:"ubuntu" echo "Bar" } } } Should both produce the same results and setup. The second point was whether we should consider not forcing things like Input (and Checkpoints or anything else that shouldn't be run inside a node) to run in an isolated Stage that then has to be visualized in your 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
[JIRA] (JENKINS-38331) per stage agent directives
Title: Message Title
Patrick Wolf edited a comment on JENKINS-38331
Re: per stage agent directives
[~michaelneale] I assumed it was a typo. Just pointing it out for anyone else reading.There were a few things. First, at a bare minimum we need per-stage agent directives when {{agent none}} is used but we should also allow per-stage directives that override any global {{agent}}.{code:java}pipeline{ agent docker:"ubuntu" stages{stage("Foo"){ agent none echo "Foo"}stage("Bar"){echo "Bar"} }}{code}and {code:java}pipeline{ agent none stages{stage("Foo"){ echo "Foo"}stage("Bar"){agent docker:"ubuntu"echo "Bar"} }} {code} Should both produce the same results and setup.The second point was whether we should consider not forcing things like Input (and Checkpoints or anything else that shouldn't be run inside a node) to run in an isolated Stage that then has to be visualized in your 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-38348) When the Github API is not responding, all jobs in the Org folder disappear.
Title: Message Title Carles Barrobés updated an issue Jenkins / JENKINS-38348 When the Github API is not responding, all jobs in the Org folder disappear. Change By: Carles Barrobés h2. Current behaviourNormally we should see our repositories and builds in the organization folder, but they are empty: !image-2016-09-19-17-57-30-814.png|thumbnail! Looking at the logs, it looks like there were issues accessing the Github API today: !image-2016-09-19-17-59-31-216.png|thumbnail! h2. Expected behaviourMy expectation would be that upon connectivity errors to Github, nothing is deleted , and we can still browse previous builds etc . Else we can't even access valid builds etc reports from active PRs that were built before connectivity issues started . 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-38348) When the Github API is not responding, all jobs in the Org folder disappear.
Title: Message Title Carles Barrobés created an issue Jenkins / JENKINS-38348 When the Github API is not responding, all jobs in the Org folder disappear. Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: image-2016-09-19-17-57-30-814.png, image-2016-09-19-17-59-31-216.png Components: github-organization-folder-plugin Created: 2016/Sep/19 4:01 PM Environment: Jenkins 2.7.4 Priority: Major Reporter: Carles Barrobés Current behaviour Normally we should see our repositories and builds in the organization folder, but they are empty:Looking at the logs, it looks like there were issues accessing the Github API today:Expected behaviour My expectation would be that upon connectivity errors to Github, nothing is deleted. Else we can't even access valid builds etc. Add Comment
[JIRA] (JENKINS-37741) gitlab oauth plugin:GitlabAPIException
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37741 Re: gitlab oauth plugin:GitlabAPIException Code changed in jenkins User: Jairo Ricarte Path: src/main/java/org/jenkinsci/plugins/GitLabRequireOrganizationMembershipACL.java http://jenkins-ci.org/commit/gitlab-oauth-plugin/9e1768a3cf3b85cf7d144b19be9a338280ff3375 Log: JENKINS-37741 Testing /project path ont allowGitlabWebHookPermission check 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-37359) Support private GitHub repositories in multibranch projects
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-37359 Support private GitHub repositories in multibranch projects Change By: Jesse Glick Labels: github private repository 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-20743) How to obtain the secret to use when starting a slave with java from a scheduled task?
Title: Message Title pjdarton commented on JENKINS-20743 Re: How to obtain the secret to use when starting a slave with java from a scheduled task? Isaac Aymerich Got in touch with a pull request that'll (a) Make the slave secret available for export to the slave via the guestinfo facility provided by JENKINS-22437 (b) Shorten the name of the slaves. Whilst I've not used that pull request as-is (numerous unrelated whitespace changes and the help wasn't entirely correct), I've created a PRs that includes the functional changes that were at the heart of this (and enhanced the help text accordingly). First PR, https://github.com/jenkinsci/vsphere-cloud-plugin/pull/56, makes the slave secret available to the guestinfo functionality as JNLP_SECRET. The second PR dealing with shortening the VM names will have to wait until https://github.com/jenkinsci/vsphere-cloud-plugin/pull/54 is merged, otherwise I'll have "merge hell". 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-37233) Switch to a responsive table component
Title: Message Title Cliff Meyers started work on JENKINS-37233 Change By: Cliff Meyers 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-38347) Github plugin dependency sporadically fails with NPE during tests
Title: Message Title Anton Tanasenko created an issue Jenkins / JENKINS-38347 Github plugin dependency sporadically fails with NPE during tests Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin Created: 2016/Sep/19 3:18 PM Priority: Minor Reporter: Anton Tanasenko GithubPlugin.postInitialize() runs Migrator.migrate(), which accesses ExtensionList through GithubPushTrigger.DescriptorImpl.get(). ExtensionsList is not usable until PLUGINS_PREPARED is attained [1] and Plugin.postInitialize() call is not guaranteed to be run after PLUGINS_PREPARED (though it does happen to run after it most of the time). In the example log [2], Migrator.migrate is run at line 368, but PLUGINS_PREPARED is only attained at 499, almost before PLUGINS_STARTED. I think the migration should be run with @Initializer(after=PLUGINS_PREPARED) to be properly working. [1] https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/ExtensionList.java#L282 [2] https://gist.github.com/atanasenko/d364aa30eb2aa07ecdb01af0e7b829be Add Comment
[JIRA] (JENKINS-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Title: Message Title Claudio Curzi updated an issue Jenkins / JENKINS-26048 Jenkins no longer cleaning up child processes when build stopped - as of 1.587 Change By: Claudio Curzi Environment: CentOS 6, JRE 7 or 8Windows Server 2008 R2, JRE 7 or 8 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-37419) Git plugin checking out non-existent submodule from different branch
Title: Message Title Sam Deane edited a comment on JENKINS-37419 Re: Git plugin checking out non-existent submodule from different branch I am seeing this too.On the face of it, it seems to be because it's picking the list of submodules from the config with `git config --get-regexp ^submodule`.That's going to pick up any submodule that's ever appeared in any branch, which seems to be a fairly ridiculous flawed approach.Perhaps I'm missing something... 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-34979) Port allocation duplicate on "Concurrent builds"
Title: Message Title Ryan Cocks commented on JENKINS-34979 Re: Port allocation duplicate on "Concurrent builds" While investigating this I also realised that the port allocator is allocating ports 'per node' rather than globally. So perhaps the actual issue is that we now have two nodes and thus if our concurrent jobs are on different nodes they can be allocated the same port. 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-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Thorsten Scherler edited a comment on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly in https://github.com/jenkinsci/blueocean-plugin/pull/499 [~michaelneale] discovered that the new syntax is not leading to the result we expected. Debugging the problem I found that there are less events send in the new syntax then the old syntaxnew syntax:!Screenshot from 2016-09-19 16-59-36.png|thumbnail! old: !Screenshot from 2016-09-19 17- 01 00 - 07 51 .png|thumbnail! !Screenshot from 2016-09-19 17- 00 01 - 51 07 .png|thumbnail! 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-37719) Build cannot be interrupted if `docker stop` hangs
Title: Message Title Cyrille Le Clerc commented on JENKINS-37719 Re: Build cannot be interrupted if `docker stop` hangs We regularly reproduce see https://gist.github.com/cyrille-leclerc/20e36ba0926b429b6ed1e485f0339334 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-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Thorsten Scherler updated an issue Jenkins / JENKINS-37962 REGRESSION: parallel karaoke not allowing branch selection or completing correctly Change By: Thorsten Scherler Attachment: Screenshot from 2016-09-19 17-01-07.png Attachment: Screenshot from 2016-09-19 17-00-51.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-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Thorsten Scherler commented on JENKINS-37962 Re: REGRESSION: parallel karaoke not allowing branch selection or completing correctly in https://github.com/jenkinsci/blueocean-plugin/pull/499 Michael Neale discovered that the new syntax is not leading to the result we expected. Debugging the problem I found that there are less events send in the new syntax then the old syntax new syntax: old: 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-37962) REGRESSION: parallel karaoke not allowing branch selection or completing correctly
Title: Message Title Thorsten Scherler updated an issue Jenkins / JENKINS-37962 REGRESSION: parallel karaoke not allowing branch selection or completing correctly Change By: Thorsten Scherler Attachment: Screenshot from 2016-09-19 16-59-36.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-26048) Jenkins no longer cleaning up child processes when build stopped - as of 1.587
Title: Message Title Piotr Paczyński commented on JENKINS-26048 Re: Jenkins no longer cleaning up child processes when build stopped - as of 1.587 For us it seems to work fine when jobs are run on master, but processes are not killed when job runs on slave (Maven job type). 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-38300) REGRESSION: Pull requests within a Github org folder / Bitbucket team not displaying
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-38300 REGRESSION: Pull requests within a Github org folder / Bitbucket team not displaying Change By: Keith Zantow Summary: REGRESSION: Pull requests within a Github org folder / Bitbucket team not displaying Issue not including the org / team folder name in the PR REST URL resulting in a 404 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-38300) REGRESSION: Pull requests within a Github org folder / Bitbucket team not displaying
Title: Message Title Keith Zantow started work on JENKINS-38300 Change By: Keith Zantow 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-38346) Rebase with upstream Subversion revision doesn't merge to HEAD
Title: Message Title Lucian Harhata updated an issue Jenkins / JENKINS-38346 Rebase with upstream Subversion revision doesn't merge to HEAD Change By: Lucian Harhata Summary: Rebase with upastream upstream Subversion revision doesn't merge to HEAD 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-38346) Rebase with upastream Subversion revision doesn't merge to HEAD
Title: Message Title Lucian Harhata created an issue Jenkins / JENKINS-38346 Rebase with upastream Subversion revision doesn't merge to HEAD Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: svnmerge-plugin Created: 2016/Sep/19 2:31 PM Priority: Critical Reporter: Lucian Harhata So i get this error: Caused by: org.tmatesoft.svn.core.SVNException: svn: E155015: One or more conflicts were produced while merging r9715:10320 into The problem is that 10320 is not the last revision number. The latest revision is 10958. Why is it merging with 10320? How can i change this? Add Comment
[JIRA] (JENKINS-37419) Git plugin checking out non-existent submodule from different branch
Title: Message Title Sam Deane commented on JENKINS-37419 Re: Git plugin checking out non-existent submodule from different branch I am seeing this too. On the face of it, it seems to be because it's picking the list of submodules from the config with `git config --get-regexp ^submodule`. That's going to pick up any submodule that's ever appeared in any branch, which seems to be a fairly ridiculous approach. Perhaps I'm missing something... 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-38341) Can't get plugins list and can't install plugins from update center
Title: Message Title Xifeng Zou commented on JENKINS-38341 Re: Can't get plugins list and can't install plugins from update center Jenkins update site can be visited with https. I changed the default update site protocol from http to https, plugins list can be fetched. But plugins url in the update-center.json are still http, install plugins failed. 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-38246) Enable viewing current github API rate status in UI
Title: Message Title Greg Smith commented on JENKINS-38246 Re: Enable viewing current github API rate status in UI No, we are using an authenticated account for access. But we can not setup github hooks – as our incoming configuration does not allow the use of those. So we are using an org scan every 15 minutes to find changes and build branches and PRs. Our org currently has 396 projects. If I set the regex for the scan to .*, it blows out the API limit right away. To fight this, I set the regex to only include a set of the projects in the scan. Not sure exactly how many the regex includes, but I'd guess probably 1/2 of the total number of projects. I did up the default github cache from the default 20M to 500M, hoping that would help a lot. It definitely seems to help some. But it seems that we have some users who don't like to wait the 15 minutes for the scan – they get impatient, and hit the build button on their builds. This also appears to use up our API rate, as the more often they do that, the more likely that we'll have some builds fail with the API rate limitation That's why I'd like to have some kind of view on what the current "used" rate is. I could get an idea of when things are going to start failing, or if I have room to add some more projects to the regex for scan. 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-28881) Add support for CloudBees folder plugin
Title: Message Title Bryan Hunt commented on JENKINS-28881 Re: Add support for CloudBees folder plugin This doesn't seem to be working with multi-branch pipeline. I see that I can set an owner for each branch pipeline job, but not the master 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-37608) Configurability of GitHub Branch Source to use Scan User with only Read permission
Title: Message Title Jesse Glick commented on JENKINS-37608 Re: Configurability of GitHub Branch Source to use Scan User with only Read permission Probably the plugin needs to be reworked to use this new API. Requires study. CC 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-36240) Default repository permission are not considered
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-36240 Default repository permission are not considered 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-19828) Kill or rework auto refresh
Title: Message Title Baptiste Mathus commented on JENKINS-19828 Re: Kill or rework auto refresh As a user, it's been years I always disable this. The few times I've used it, it's screwed a form I was filling in and so on. So we should indeed either: simply kill it in the main code, or offer a simple way for people to simply disable it totally. Like Oleg says: if the UI has a value of 0 e.g., just do not display the field at all. We could probably even use it as a progressive strategy to kill it: do that, plus define the default to 0 for new installs? And in the meantime, make a poll about that on the users list to take the temperature? 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-18781) Configurable channel timeout for slaves
Title: Message Title
Joe George edited a comment on JENKINS-18781
Re: Configurable channel timeout for slaves
According to the documentation (https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread) {{-Dhudson.slaves.ChannelPinger.pingInterval=1}} should be set on Master? _Master_. You should also try setting {{-Dhudson.remoting.Launcher.pingIntervalSec=-1}} on the Slave. I haven't experience any issues since disabling pinging this way. Next is to start testing different timeout values.
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-18781) Configurable channel timeout for slaves
Title: Message Title Joe George commented on JENKINS-18781 Re: Configurable channel timeout for slaves According to the documentation (https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread) -Dhudson.slaves.ChannelPinger.pingInterval=1 should be set on Master? You should also try setting -Dhudson.remoting.Launcher.pingIntervalSec=-1 on the Slave. I haven't experience any issues since disabling pinging this way. Next is to start testing different timeout values. 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-36318) No Configuration UI
Title: Message Title Brian Krische commented on JENKINS-36318 Re: No Configuration UI Yup, looks like it's under Global Tool Configuration and not Configure System like the documentation says. 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-38143) Refactor of Capabilities on backend
Title: Message Title Cliff Meyers commented on JENKINS-38143 Re: Refactor of Capabilities on backend James Dumay no, there is still work to do on this ticket. I believe Vivek has a PR for 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-33698) NodeJS plugin npm install without root permissions
Title: Message Title Nikolas Falco commented on JENKINS-33698 Re: NodeJS plugin npm install without root permissions There is a PR#13 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-36210) expose details through REST API
Title: Message Title Ignacio Albors commented on JENKINS-36210 Re: expose details through REST API Where do you expect to find this information? I mean, in "/view//api/json?pretty=true=3" there is no data exposed related to any widget. And, AFAIK, there's no way to show it in that kind of URL (bound to a View). Would it be ok an independent URL only for this widget? 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-18781) Configurable channel timeout for slaves
Title: Message Title Markus Niklasson edited a comment on JENKINS-18781 Re: Configurable channel timeout for slaves Hi,We have recently also encountered disconnection issues. Slave is a Windows 7 (x64) PC with enough of RAM and CPU to run heavy applications. The Jenkins master is a Enterprise Redhat 7 (3.10.0-327.18.2.el7.x86_64) running Jenkins 2.23 also with enough memory and so on to run Jenkins. Both running Java 8 update 102. The slave are connected through JNLP. Network can be a bit unstable at times.The following intermittent error occurs very frequently during builds:Agent went offline during the buildERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@69c08f2a[name=Buildserver] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: java.io.IOException: Connection timed out at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 6 moreI have unticked "Response Time" from "Preventive Node Monitoring" and Slaves has -Dhudson.slaves.ChannelPinger.pingInterval=1 set.Any other workaround available? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-18781) Configurable channel timeout for slaves
Title: Message Title Markus Niklasson commented on JENKINS-18781 Re: Configurable channel timeout for slaves Hi, We have recently also encountered disconnection issues. Slave is a Windows 7 (x64) PC with enough of RAM and CPU to run heavy applications. The Jenkins master is a Enterprise Redhat 7 (3.10.0-327.18.2.el7.x86_64) also with enough memory and so on to run Jenkins. Both running Java 8 update 102. The slave are connected through JNLP. Network can be a bit unstable at times. The following intermittent error occurs very frequently during builds: Agent went offline during the build ERROR: Connection was broken: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@69c08f2a[name=Buildserver] at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:208) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:629) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Connection timed out at sun.nio.ch.FileDispatcherImpl.read0(Native Method) at sun.nio.ch.SocketDispatcher.read(Unknown Source) at sun.nio.ch.IOUtil.readIntoNativeBuffer(Unknown Source) at sun.nio.ch.IOUtil.read(Unknown Source) at sun.nio.ch.SocketChannelImpl.read(Unknown Source) at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:137) at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:310) at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:561) ... 6 more I have unticked "Response Time" from "Preventive Node Monitoring" and Slaves has -Dhudson.slaves.ChannelPinger.pingInterval=1 set. Any other workaround available? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38243) NPE when RESERVED attribute content is empty
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38243 Re: NPE when RESERVED attribute content is empty Code changed in jenkins User: Scott Hebert Path: src/main/java/com/redhat/foreman/ForemanAPI.java src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/e2e8aa236512d126d57fb2aadac918b1ad55676e Log: Merge pull request #5 from pjanouse/JENKINS-38243 JENKINS-38243 Fixed unhandled NPE, added @CheckForNull annotation Compare: https://github.com/jenkinsci/foreman-node-sharing-plugin/compare/e1b4524c1cef...e2e8aa236512 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-38243) NPE when RESERVED attribute content is empty
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38243 Re: NPE when RESERVED attribute content is empty Code changed in jenkins User: Ing. Pavel Janousek Path: src/main/java/com/redhat/foreman/ForemanAPI.java src/main/java/com/redhat/foreman/ForemanSharedNodeCloud.java http://jenkins-ci.org/commit/foreman-node-sharing-plugin/b7faa5d63a23c9d9cc719e10351c4aaf670d536a Log: JENKINS-38243 Fixed unhandled NPE, added @CheckForNull annotation 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-27238) Inject parameters on manual build trigger
Title: Message Title Marek Kapowicki edited a comment on JENKINS-27238 Re: Inject parameters on manual build trigger i also agree with RobertI ve just linked the similar issue refers to delivery-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-27238) Inject parameters on manual build trigger
Title: Message Title Marek Kapowicki commented on JENKINS-27238 Re: Inject parameters on manual build trigger i also agree with Robert I ve just linked the similar issue refers to delivery-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-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Hendrik Brinkmann edited a comment on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
Your git-url starts with {{https://}}. Is your credential a username with password or a private ssh-key . ? If the latter applied, I would expect an url that starts with {{ssh://}}{code:xml} https://git.netent.com/scm/ngp/jenkins-workflow-libs.git{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 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-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title Hendrik Brinkmann commented on JENKINS-38048 Re: Credentials dropdowns empty when configuring external libraries at the global level Your Git-Url starts with https://. Is your credential a username with password or a private ssh-key. If the latter applied, I would expect an url that starts with ssh:// https://git.netent.com/scm/ngp/jenkins-workflow-libs.git 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-38048) Credentials dropdowns empty when configuring external libraries at the global level
Title: Message Title
Hendrik Brinkmann edited a comment on JENKINS-38048
Re: Credentials dropdowns empty when configuring external libraries at the global level
Your Git git - Url url starts with {{https://}}. Is your credential a username with password or a private ssh-key. If the latter applied, I would expect an url that starts with {{ssh://}}{code:xml} https://git.netent.com/scm/ngp/jenkins-workflow-libs.git{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 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-34896) Not retrieving teams
Title: Message Title Lior Goikhburg commented on JENKINS-34896 Re: Not retrieving teams Having the same problem. The plugin works well with users, but not with teams. 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-38315) Please wait while Jenkins is getting ready to work
Title: Message Title andrew jones edited a comment on JENKINS-38315 Re: Please wait while Jenkins is getting ready to work Hi Mark,I’d agree with you that this is likely to be something related to the environment that’s causing this issue. The logs are precisely the problem I’m having, I’m not seeing any messages that are giving me a good starting point. I’ve left Jenkins running for about 12 hours hoping something would cause a timeout to occur that may point to a hung process or something.So fat today I’ve done a back to back test on jdk-7u79-linux-x64.rpmandjdk-8u101-linux-x64.rpm I got the same behaviour from both. I'll attach some output from the logs.If I just run that war file I get[root@ftdcslbinf523 jenkins]# /usr/java/jdk1.7.0_79/bin/java -jar jenkins.war --debugRunning from: /usr/lib/jenkins/jenkins.warwebroot: $user.home/.jenkinsException in thread "main" java.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at Main._main(Main.java:246)at Main.main(Main.java:91)Caused by: java.lang.NumberFormatException: For input string: "true"at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)at java.lang.Integer.parseInt(Integer.java:492)at java.lang.Integer.parseInt(Integer.java:527)at winstone.cmdline.Option.intArg(Option.java:291)at winstone.Launcher.initLogger(Launcher.java:411)at winstone.cmdline.CmdLineParser.parse(CmdLineParser.java:83)at winstone.Launcher.getArgsFromCommandLine(Launcher.java:359)at winstone.Launcher.main(Launcher.java:332)... 6 moreBut I expect that’s more down to one of the args missing.I'll add the putout out put from a command line startup rather than using the init.d script. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Paul Allen - hope the conference was a good one for you. Just curious if I helped make the issue more clear. Fingers crossed that you have time to take a look and help (I think it's just a problem with files in the excluded list not syncing to the latest due to the quiet period). If I can test or do anything, just let me know. 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-38315) Please wait while Jenkins is getting ready to work
Title: Message Title andrew jones updated an issue Jenkins / JENKINS-38315 Please wait while Jenkins is getting ready to work Change By: andrew jones Attachment: manualstartup.txt 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-38315) Please wait while Jenkins is getting ready to work
Title: Message Title andrew jones commented on JENKINS-38315 Re: Please wait while Jenkins is getting ready to work Hi Mark, I’d agree with you that this is likely to be something related to the environment that’s causing this issue. The logs are precisely the problem I’m having, I’m not seeing any messages that are giving me a good starting point. I’ve left Jenkins running for about 12 hours hoping something would cause a timeout to occur that may point to a hung process or something. So fat today I’ve done a back to back test on jdk-7u79-linux-x64.rpm and jdk-8u101-linux-x64.rpm I got the same behaviour from both. I'll attach some output from the logs. If I just run that war file I get [root@ftdcslbinf523 jenkins]# /usr/java/jdk1.7.0_79/bin/java -jar jenkins.war --debug Running from: /usr/lib/jenkins/jenkins.war webroot: $user.home/.jenkins Exception in thread "main" java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at Main._main(Main.java:246) at Main.main(Main.java:91) Caused by: java.lang.NumberFormatException: For input string: "true" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) at java.lang.Integer.parseInt(Integer.java:492) at java.lang.Integer.parseInt(Integer.java:527) at winstone.cmdline.Option.intArg(Option.java:291) at winstone.Launcher.initLogger(Launcher.java:411) at winstone.cmdline.CmdLineParser.parse(CmdLineParser.java:83) at winstone.Launcher.getArgsFromCommandLine(Launcher.java:359) at winstone.Launcher.main(Launcher.java:332) ... 6 more But I expect that’s more down to one of the args missing. I'll add the putout from a command line startup rather than using the init.d script. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38315) Please wait while Jenkins is getting ready to work
Title: Message Title andrew jones updated an issue Jenkins / JENKINS-38315 Please wait while Jenkins is getting ready to work Change By: andrew jones Attachment: logs.txt 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-38315) Please wait while Jenkins is getting ready to work
Title: Message Title
andrew jones updated an issue
Jenkins / JENKINS-38315
Please wait while Jenkins is getting ready to work
Change By:
andrew jones
Comment:
-bash-4.2$ /usr/java/jdk1.7.0_79/bin/java -Djava.awt.headless=true -jar /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080Running from: /usr/share/jenkins/jenkins.warSep 19, 2016 7:07:54 AM org.eclipse.jetty.util.log.JavaUtilLog infoINFO: Logging initialized @468msSep 19, 2016 7:07:54 AM winstone.Logger logInternalINFO: Beginning extraction from war file+**Sep 19, 2016 7:07:54 AM org.eclipse.jetty.util.log.JavaUtilLog warnWARNING: Empty contextPath**+Sep 19, 2016 7:07:54 AM org.eclipse.jetty.util.log.JavaUtilLog infoINFO: jetty-9.2.z-SNAPSHOTSep 19, 2016 7:07:55 AM org.eclipse.jetty.util.log.JavaUtilLog infoINFO: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServletJenkins home directory: /var/lib/jenkins/.jenkins found at: $user.home/.jenkinsSep 19, 2016 7:07:56 AM org.eclipse.jetty.util.log.JavaUtilLog infoINFO: Started w.@7e938520{/,file:/var/cache/jenkins/war/,AVAILABLE}{/var/cache/jenkins/war}Sep 19, 2016 7:07:56 AM org.eclipse.jetty.util.log.JavaUtilLog infoINFO: Started ServerConnector@51499e81{HTTP/1.1}{0.0.0.0:8080}Sep 19, 2016 7:07:56 AM org.eclipse.jetty.util.log.JavaUtilLog infoINFO: Started @2041msSep 19, 2016 7:07:56 AM winstone.Logger logInternalINFO: Winstone Servlet Engine v2.0 running: controlPort=disabledSep 19, 2016 7:07:56 AM jenkins.InitReactorRunner$1 onAttainedINFO: Started initializationSep 19, 2016 7:07:56 AM jenkins.InitReactorRunner$1 onAttainedINFO: Listed all pluginsSep 19, 2016 7:07:58 AM jenkins.InitReactorRunner$1 onAttainedINFO: Prepared all pluginsSep 19, 2016 7:07:58 AM jenkins.InitReactorRunner$1 onAttainedINFO: Started all pluginsSep 19, 2016 7:07:58 AM jenkins.InitReactorRunner$1 onAttainedINFO: Augmented all extensionsSep 19, 2016 7:07:59 AM jenkins.InitReactorRunner$1 onAttainedINFO: Loaded all jobsSep 19, 2016 7:07:59 AM hudson.model.AsyncPeriodicWork$1 runINFO: Started Download metadataSep 19, 2016 7:08:01 AM org.springframework.context.support.AbstractApplicationContext prepareRefreshINFO: Refreshing org.springframework.web.context.support.StaticWebApplicationContext@1d68c8e7: display name [Root WebApplicationContext]; startup date [Mon Sep 19 07:08:01 CDT 2016]; root of context hierarchySep 19, 2016 7:08:01 AM org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactoryINFO: Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@1d68c8e7]: org.springframework.beans.factory.support.DefaultListableBeanFactory@54589392Sep 19, 2016 7:08:01 AM org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletonsINFO: Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@54589392: defining beans [authenticationManager]; root of factory hierarchySep 19, 2016 7:08:01 AM org.jenkinsci.main.modules.sshd.SSHD startINFO: Started SSHD at port 34900Sep 19, 2016 7:08:01 AM jenkins.InitReactorRunner$1 onAttainedINFO: Completed initializationSep 19, 2016 7:08:01 AM org.springframework.context.support.AbstractApplicationContext
