[JIRA] (JENKINS-39687) Configuration section doesn't appear
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39687 Re: Configuration section doesn't appear Code changed in jenkins User: Daniel Lo Nigro Path: src/main/resources/org/jenkinsci/plugins/githubissues/GitHubIssueNotifier/global.jelly src/main/resources/org/jenkinsci/plugins/githubissues/GitHubIssueNotifier/help-issueBody.html src/main/resources/org/jenkinsci/plugins/githubissues/GitHubIssueNotifier/help-issueTag.html src/main/resources/org/jenkinsci/plugins/githubissues/GitHubIssueNotifier/help-issueTitle.html src/main/resources/org/jenkinsci/plugins/githubissues/GithubIssueNotifier/global.jelly src/main/resources/org/jenkinsci/plugins/githubissues/GithubIssueNotifier/help-issueBody.html src/main/resources/org/jenkinsci/plugins/githubissues/GithubIssueNotifier/help-issueTag.html src/main/resources/org/jenkinsci/plugins/githubissues/GithubIssueNotifier/help-issueTitle.html http://jenkins-ci.org/commit/github-issues-plugin/13b6c4eb8d772a88d04aaf37099e1effaef82b40 Log: Fix JENKINS-39687 - Capitalization of GitHubIssueNotifier directory was incorrect. #close 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-39687) Configuration section doesn't appear
Title: Message Title Daniel Lo Nigro closed an issue as Fixed Jenkins / JENKINS-39687 Configuration section doesn't appear Change By: Daniel Lo Nigro Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39687) Configuration section doesn't appear
Title: Message Title Daniel Lo Nigro created an issue Jenkins / JENKINS-39687 Configuration section doesn't appear Issue Type: Bug Assignee: Daniel Lo Nigro Components: github-issues-plugin Created: 2016/Nov/12 7:19 AM Priority: Major Reporter: Daniel Lo Nigro The configuration section doesn't appear Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39662) NPE with multi-config project
Title: Message Title Daniel Lo Nigro closed an issue as Fixed Jenkins / JENKINS-39662 NPE with multi-config project Change By: Daniel Lo Nigro Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39662) NPE with multi-config project
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39662 Re: NPE with multi-config project Code changed in jenkins User: Daniel Lo Nigro Path: src/main/java/org/jenkinsci/plugins/githubissues/GitHubIssueNotifier.java src/main/java/org/jenkinsci/plugins/githubissues/exceptions/GitHubRepositoryException.java http://jenkins-ci.org/commit/github-issues-plugin/b473330e7b889a4ca784b132e3b561a91ff75bb4 Log: Fix JENKINS-39662: NullPointerException for multi-config projects #close 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-37658) Github-branch-source plugin should support git plugin extensions
Title: Message Title Christian Höltje commented on JENKINS-37658 Re: Github-branch-source plugin should support git plugin extensions But that doesn't make sense when using the github org folders. Different repos would want different settings. Also you can't set them in github org folders. 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-22178) Publish artifacts to Jclouds Cloud Storage - cannot publish on failure
Title: Message Title Fritz Elfert resolved as Fixed Fixed in current git. Jenkins / JENKINS-22178 Publish artifacts to Jclouds Cloud Storage - cannot publish on failure Change By: Fritz Elfert Status: Open Resolved Assignee: Fritz Elfert 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
[JIRA] (JENKINS-22178) Publish artifacts to Jclouds Cloud Storage - cannot publish on failure
Title: Message Title Fritz Elfert stopped work on JENKINS-22178 Change By: Fritz Elfert Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22178) Publish artifacts to Jclouds Cloud Storage - cannot publish on failure
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22178 Re: Publish artifacts to Jclouds Cloud Storage - cannot publish on failure Code changed in jenkins User: Fritz Elfert Path: jclouds-plugin/src/main/java/jenkins/plugins/jclouds/blobstore/BlobStoreEntry.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/blobstore/BlobStoreProfile.java jclouds-plugin/src/main/java/jenkins/plugins/jclouds/blobstore/BlobStorePublisher.java jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/blobstore/BlobStoreEntry/config.jelly jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/blobstore/BlobStoreEntry/help-allowEmptyFileset.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/blobstore/BlobStoreEntry/help-container.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/blobstore/BlobStoreEntry/help-keepHierarchy.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/blobstore/BlobStoreEntry/help-path.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/blobstore/BlobStoreEntry/help-sourceFile.html jclouds-plugin/src/main/resources/jenkins/plugins/jclouds/blobstore/BlobStoreProfile/config.jelly http://jenkins-ci.org/commit/jclouds-plugin/a64126f16e33f5182966db8eb869c3bfc25f8938 Log: Fixed JENKINS-22178 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-39661) Investigate performance of Pipeline /activity and /runs REST endpoint
Title: Message Title James Dumay commented on JENKINS-39661 Re: Investigate performance of Pipeline /activity and /runs REST endpoint Tom FENNELLY I think Vivek Pandey had some ideas about this one - maybe sync up? 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-39686) PersistentVolumeClaim settings form empty
Title: Message Title paolo mainardi created an issue Jenkins / JENKINS-39686 PersistentVolumeClaim settings form empty Issue Type: Bug Assignee: Carlos Sanchez Attachments: Screen Shot 2016-11-12 at 00.31.05.png Components: kubernetes-plugin Created: 2016/Nov/11 11:39 PM Environment: Jenkins ver. 2.27 - Plugin 0.90 Labels: volumes Priority: Critical Reporter: paolo mainardi The persistent volume claim settings form is empty, if i understood well the plugin it's supposed to render this form: https://github.com/jenkinsci/kubernetes-plugin/blob/f2be842b9b2e24624e556f278e57fa4ec44d2557/src/main/resources/org/csanchez/jenkins/plugins/kubernetes/volumes/PvcVolume/config.jelly but as you can see in the attachment nothing happen.
[JIRA] (JENKINS-38348) GitHub API errors result in jobs being incorrectly deleted
Title: Message Title Evan Borgstrom updated an issue Jenkins / JENKINS-38348 GitHub API errors result in jobs being incorrectly deleted Change By: Evan Borgstrom Summary: When the Github GitHub API is not responding, all jobs errors result in the Org folder disappear. jobs being incorrectly deleted 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
Evan Borgstrom edited a comment on JENKINS-38348
Re: When the Github API is not responding, all jobs in the Org folder disappear.
This also occurs if you hit the rate limit while scanning:{noformat}Nov 10, 2016 2:30:35 PM INFO jenkins.branch.WorkspaceLocatorImpl$Deleter cleanUpdeleting obsolete workspace /var/lib/jenkins/workspace/... Nov 10, 2016 2:30:35 PM WARNING org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl maybeApplyFailed to apply GitHub Org Folder theme to GitHub/...org.jenkinsci.plugins.github_branch_source.RateLimitExceededException: GitHub API rate limit exceeded{noformat}I agree that this is a rather serious problem and that these errors should *not* make the jobs disappear. It was very unexpected to lose all of our build history. We use the Artifactory plugin and remove artifacts as we clean up builds, so this means that we will end up leaving some builds orphaned in Artifactory and lose out on being able to trace artifacts back to builds.
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 Evan Borgstrom commented on JENKINS-38348 Re: When the Github API is not responding, all jobs in the Org folder disappear. This also occurs if you hit the rate limit while scanning: Nov 10, 2016 2:30:35 PM INFO jenkins.branch.WorkspaceLocatorImpl$Deleter cleanUp deleting obsolete workspace /var/lib/jenkins/workspace/... Nov 10, 2016 2:30:35 PM WARNING org.jenkinsci.plugins.orgfolder.github.ItemListenerImpl maybeApply Failed to apply GitHub Org Folder theme to GitHub/... org.jenkinsci.plugins.github_branch_source.RateLimitExceededException: GitHub API rate limit exceeded I agree that this is a rather serious problem and that these errors should make the jobs disappear. It was very unexpected to lose all of our build history. We use the Artifactory plugin and remove artifacts as we clean up builds, so this means that we will end up leaving some builds orphaned in Artifactory and lose out on being able to trace artifacts back to builds. 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-34500) Pipeline Plugin - pipeline-stage-step
Title: Message Title Matt Evans closed an issue as Won't Do Fixed by https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Milestone+Step+Plugin Jenkins / JENKINS-34500 Pipeline Plugin - pipeline-stage-step Change By: Matt Evans Status: Open Closed Resolution: Won't Do 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-38721) Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy
Title: Message Title Jesse Glick commented on JENKINS-38721 Re: Viewing canceled Pipeline jobs can get NPE from UserInterruption/summary.groovy Can you link your PR please? 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-39685) Failure to load shared libraries doesn't display any flow graph
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-39685 Failure to load shared libraries doesn't display any flow graph Issue Type: Bug Assignee: CloudBees Inc. Attachments: failed-shared-library-classic-console.png, failed-shared-library-classic-main.png, failed-shared-library.png Components: blueocean-plugin Created: 2016/Nov/11 10:18 PM Priority: Minor Reporter: R. Tyler Croy I have a Pipeline Shared Library configured for a folder which has recently stopped working. The screenshot attached shows how this is rendered in Blue Ocean, which I'm not sure is "good" but I thought I would at least let James Dumay Add Comment
[JIRA] (JENKINS-39684) Use docker images from private registry
Title: Message Title Patrick Wolf commented on JENKINS-39684 Re: Use docker images from private registry Michael Neale James Dumay Do you guys have any suggestions for the syntax? 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-39684) Use docker images from private registry
Title: Message Title
Patrick Wolf created an issue
Jenkins / JENKINS-39684
Use docker images from private registry
Issue Type:
Story
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Nov/11 9:51 PM
Priority:
Minor
Reporter:
Patrick Wolf
When using an agent directive in Declarative Pipeline there is no way to specify the Docker Registry to use. In Scripted Pipline this is available via the withRegistry wrapper
docker.withRegistry('https://docker.mycorp.com/', 'docker-login') {
git '…'
docker.build('myapp').push('latest')
}
For Declarative we should allow admins to create a default registry to be used by all Pipelines at the master level or the folder level. We should also allow a specific registry setting in the language itself via the agent directive.
Add Comment
[JIRA] (JENKINS-39683) 500 error preventing flow graph and steps from showing :(
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-39683 500 error preventing flow graph and steps from showing :( Issue Type: Bug Assignee: CloudBees Inc. Attachments: api-500.png Components: blueocean-plugin Created: 2016/Nov/11 9:36 PM Environment: Jenkins 2.19.1, Blue Ocean built at 31st October 2016 05:16 PM , · 915bc21 Priority: Minor Reporter: R. Tyler Croy I'm not sure what the reproduction steps are, but got this on this view In the system.log Error while serving https://ci.jenkins.io/blue/rest/organizations/jenkins/pipelines/Infra/plugin-site-api/branches/master/runs/19/nodes/ java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor1392.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:324) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:196) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at
[JIRA] (JENKINS-25616) Support for coverage.xml generated by Android tools
Title: Message Title centic commented on JENKINS-25616 Re: Support for coverage.xml generated by Android tools JENKINS-28652 was solved in a different way due to lack of dev-time, so unless someone with enough time and skill steps in, this likely won't be available anytime soon, sorry. 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-39655) Adding JIRA plugin throws NullPointerException
Title: Message Title sreejitha vijayan commented on JENKINS-39655 Re: Adding JIRA plugin throws NullPointerException the jira url I specified was http://localhost:2990/jira I am actually using the JiraTestResultReporter Plugin ver 2.0.3 and the JIRA Plugin ver 2.2.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39682) Generated Mutlibranch Pipeline Job does not index branches
Title: Message Title
Patrick Wolf created an issue
Jenkins / JENKINS-39682
Generated Mutlibranch Pipeline Job does not index branches
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2016/Nov/11 9:27 PM
Priority:
Minor
Reporter:
Patrick Wolf
Using a JobDSL script to generate a multibranch Pipeline job does not trigger a branch index to find Jenkinsfile Here is a simple dsl job
multibranchPipelineJob(repo) {
branchSources {
github {
scanCredentialsId(credentials)
repoOwner(credentials)
repository(repo)
}
}
}
Using this created the job fine but did not trigger a branch scan until I manually triggered a branch index. It also works if you open the multibranch job configuration and save it with no changes. Creating a multibranch job directly from the UI works fine. The only way I can trigger a branch index is to add a triggers section to the command to periodically scan every minute. I then had to create 3 build steps: 1. JobDSL to create mutlibranch Pipeline job with a trigger set to 1 minute 2. Shell step to Sleep for 60 seconds 3. JobDSL to modify the multibranch Pipeline job and turn off the trigger.
[JIRA] (JENKINS-39655) Adding JIRA plugin throws NullPointerException
Title: Message Title sreejitha vijayan edited a comment on JENKINS-39655 Re: Adding JIRA plugin throws NullPointerException the jira url I specified was http://localhost:2990/jiraI am actually using the JiraTestResultReporter Plugin ver 2.0.3 and the JIRA Plugin ver 2.2.1 and I see the same issue in both cases Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException
Title: Message Title Brenna Flood commented on JENKINS-24385 Re: Jenkins CLI hangs with InvocationTargetException I experienced this issue. My setup: Jenkins 2.7.4 - 2.11.11 Docker - CentOS 6.8 JDK 1.8.111 No security setup (this is a test instance - chef + kitchen) The cause of the behavior in my case was that the identity file in the Jenkins root could not be loaded. To correct the issue, I simply removed the file and restarted the Jenkins service. 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title Andres Rodriguez updated JENKINS-39672 Jenkins / JENKINS-39672 Token-macro PCT issues against 2.91.x Change By: Andres Rodriguez 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-39681) Creating a pipeline with a duplicate name returns a 500 error
Title: Message Title Cliff Meyers updated an issue Jenkins / JENKINS-39681 Creating a pipeline with a duplicate name returns a 500 error Change By: Cliff Meyers Issue Type: Task Bug 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-39681) Creating a pipeline with a duplicate name returns a 500 error
Title: Message Title
Cliff Meyers created an issue
Jenkins / JENKINS-39681
Creating a pipeline with a duplicate name returns a 500 error
Issue Type:
Task
Assignee:
Vivek Pandey
Components:
blueocean-plugin
Created:
2016/Nov/11 8:56 PM
Priority:
Minor
Reporter:
Cliff Meyers
Repro Steps: 1. Make a request to create a repo from Github
cbrmbp:blueocean cmeyers$ curl -v -u cmeyers:cmeyers -H 'Content-Type: application/json' http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/ -d '{ "name" : "test-1", "creatorId" : "io.jenkins.blueocean.blueocean_github_pipeline.GithubPipelineCreatorImpl", "scmConfig" : { "credentialId": "10182e26-a313-43d4-9226-afa6bcb856eb", "config": { "orgName": "cliffmeyers", "repos" : [ "jenkinsfile-experiments" ] } } }'
* Trying ::1...
* Connected to localhost (::1) port 8080 (#0)
* Server auth using Basic with user 'cmeyers'
> POST /jenkins/blue/rest/organizations/jenkins/pipelines/ HTTP/1.1
> Host: localhost:8080
> Authorization: Basic Y21leWVyczpjbWV5ZXJz
> User-Agent: curl/7.43.0
> Accept: */*
> Content-Type: application/json
> Content-Length: 266
>
* upload completely sent off: 266 out of 266 bytes
< HTTP/1.1 201 Created
< Date: Fri, 11 Nov 2016 20:48:11 GMT
< X-Content-Type-Options: nosniff
< Stapler-Trace-001: -> evaluate( :hudson.model.Hudson,"/blue/rest/organizations/jenkins/pipelines")
< Stapler-Trace-002: ->
[JIRA] (JENKINS-26134) Shorter syntax for unarchive
Title: Message Title Mark Stosberg commented on JENKINS-26134 Re: Shorter syntax for unarchive David McFarland has a good point. 'unarchive' is useful when you do want to archive things permanently. Both stashing and archiving things seems like a pain. unstash does not replace unarchive completely, as the former deals with temporary data, while the latter deals with data you want to keep permanently. 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-38585) User can add a new step from the list of available steps and edit it
Title: Message Title Keith Zantow started work on JENKINS-38585 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-39680) httpRequest method in Pipeline causes weird behavior
Title: Message Title
Tyrel Haveman created an issue
Jenkins / JENKINS-39680
httpRequest method in Pipeline causes weird behavior
Issue Type:
Bug
Assignee:
Janario Oliveira
Components:
http-request-plugin
Created:
2016/Nov/11 8:32 PM
Environment:
Jenkins 2.19.2 HTTP Request Plugin 1.18.12
Labels:
http https pipeline groovy
Priority:
Blocker
Reporter:
Tyrel Haveman
We're running into an issue with httpRequest in a Groovy script used on a mutlibranch pipeline job. I have code that looks something like this:
/ Jenkinsfile /
// ...
notify = load 'notify.groovy'
// ...
if (checkResults(...) > 0) {
println 'Tests failed, stopping build'
return 1
}
int checkResults(...) {
// ...
notify.buildFailed(...)
return failedTestCount
}
/ notify.groovy /
void buildFailed(...) {
// ...
sendMessage(...)
}
void sendMessage(...) {
// ...
def response = httpRequest acceptType: 'APPLICATION_JSON', contentType: 'APPLICATION_JSON',
httpMode: 'POST', requestBody: body, consoleLogResponseBody: true,
url: 'https://example.net/hooks/4ezwZwLYbmYwJmD6MXN6yH3YNdd/C6m5uKJstArcKQyxfBYb5nMW7PkPSriACsXg9w',
validResponseContent: '"success":true'
println "Sent a notification, got a $response.status response"
}
Expected Results When
[JIRA] (JENKINS-39680) httpRequest method in Pipeline causes weird behavior
Title: Message Title
Tyrel Haveman updated an issue
Jenkins / JENKINS-39680
httpRequest method in Pipeline causes weird behavior
Change By:
Tyrel Haveman
We're running into an issue with {{httpRequest}} in a Groovy script used on a mutlibranch pipeline job.I have code that looks something like this:{code:java}/ Jenkinsfile /// ...notify = load 'notify.groovy'// ...if (checkResults(...) > 0) {println 'Tests failed, stopping build'return 1}int checkResults(...) {// ...notify.buildFailed(...)return failedTestCount}/ notify.groovy /void buildFailed(...) { // ... sendMessage(...)}void sendMessage(...) { // ... def response = httpRequest acceptType: 'APPLICATION_JSON', contentType: 'APPLICATION_JSON',httpMode: 'POST', requestBody: body, consoleLogResponseBody: true,url: 'https://example.net/hooks/4ezwZwLYbmYwJmD6MXN6yH3YNdd/C6m5uKJstArcKQyxfBYb5nMW7PkPSriACsXg9w',validResponseContent: '"success":true' println "Sent a notification, got a $response.status response"}{code}h2. Expected ResultsWhen this code runs, I expect for the {{httpRequest}} to return the response, the code to get printed out from my {{println}}, then {{checkResults}} to return the number of failed tests it detected (code not shown). However, that's not what happens.h2. Actual ResultsInstead, {{sendMessage }} immediately return without executing my {{println}}, and most oddly of all, {{checkResults}} ends up returning the HTTP Response from {{httpRequest}}! How is this even possible?The symptom, other than my {{println}} doing nothing, is that the {{> 0}} comparison in the {{Jenkinsfile}} doesn't work and this exception is thrown:{noformat}groovy.lang.GroovyRuntimeException: Cannot compare jenkins.plugins.http_request.ResponseContentSupplier with value 'Status: 200, Response: {"success":true}' and java.lang.Integer with value '0'{noformat}It's possible that I'm doing something wrong here, but this seems very much like a bug. It's hard for me to imagine what I could do wrong that would cause the stack to get blown apart in such a way.
Add Comment
[JIRA] (JENKINS-16950) Can't remove sort of phases in multijob project
Title: Message Title Greg Parsons commented on JENKINS-16950 Re: Can't remove sort of phases in multijob project +1 this is a pain! 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-39677) docker-workflow plugin is not available in update site
Title: Message Title Roman Safronov commented on JENKINS-39677 Re: docker-workflow plugin is not available in update site Same about http://updates.jenkins-ci.org/download/plugins. There is no "docker-worflow" Now I'm building it from sources to unblock my CI server updade 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-39679) Use maven-plugin interceptor for maven project integration
Title: Message Title Anton Lundin created an issue Jenkins / JENKINS-39679 Use maven-plugin interceptor for maven project integration Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2016/Nov/11 8:07 PM Priority: Minor Reporter: Anton Lundin pipeline-maven-plugin should leverage the integration done with maven-plugin aganst jenkins, where you can get automatic fingerprinting, junit archiving, mojo timing formation and so on. Add Comment This message was sent
[JIRA] (JENKINS-39678) Multijob does not allow one to set labels to downstream jobs
Title: Message Title Greg Parsons created an issue Jenkins / JENKINS-39678 Multijob does not allow one to set labels to downstream jobs Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 2016/Nov/11 7:51 PM Priority: Minor Reporter: Greg Parsons Use case: Multijob 1 is calling Job X twice, where each call is a different set of parameters. Issue: Each repeat of Job X looks the same in the list of the multijob. I would like to be able to give them a label that specifies more detail about why this job is called multiple times. Current workaround is to create a new phase with a name, but you lose concurrency. Request: I would like to be able to give the downstream job a label in the Multijob pipeline. Add Comment
[JIRA] (JENKINS-39562) Jenkins 2.19.2 returns "Forbidden" when configured for WildFly Deployer Plugin
Title: Message Title Vance Gloster commented on JENKINS-39562 Re: Jenkins 2.19.2 returns "Forbidden" when configured for WildFly Deployer Plugin As a workaround, you can use a shell script, as described here: https://blog.codecentric.de/en/2015/01/automated-wildfly-deployments-shell-scripting/ 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-21248) Add shallow update init for submodule
Title: Message Title alex karpinski commented on JENKINS-21248 Re: Add shallow update init for submodule +1 from me too. A clone takes 6min instead of 9sec because I can't do a shallow update. This would really help. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39677) docker-workflow plugin is not available in update site
Title: Message Title Roman Safronov created an issue Jenkins / JENKINS-39677 docker-workflow plugin is not available in update site Issue Type: Bug Assignee: Unassigned Components: docker-workflow-plugin Created: 2016/Nov/11 7:24 PM Priority: Minor Reporter: Roman Safronov I can't install "docker-workflow" plugin, it's just not available on update site. https://updates.jenkins-ci.org/current/update-center.json does not contain entry for "docker-workflow" plugin. Add Comment This message was
[JIRA] (JENKINS-39677) docker-workflow plugin is not available in update site
Title: Message Title Roman Safronov updated an issue Jenkins / JENKINS-39677 docker-workflow plugin is not available in update site Change By: Roman Safronov Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38584) REST API for fetching available steps
Title: Message Title Keith Zantow updated JENKINS-38584 Jenkins / JENKINS-38584 REST API for fetching available steps Change By: Keith Zantow Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39676) Cannot populate servers via groovy script
Title: Message Title Sebastian Maj updated an issue Jenkins / JENKINS-39676 Cannot populate servers via groovy script Change By: Sebastian Maj Environment: ava Centos 7.2java -1.8.0-openjdk-1.8.0.111-1.b15.el7_2jenkins-2.19.2-1.1Active Directory plugin 2.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39676) Cannot populate servers via groovy script
Title: Message Title Sebastian Maj updated an issue Jenkins / JENKINS-39676 Cannot populate servers via groovy script Change By: Sebastian Maj Environment: ava-1.8.0-openjdk-1.8.0.111-1.b15.el7_2 jenkins-2.19.2-1.1Active Directory plugin 2.0 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39676) Cannot populate servers via groovy script
Title: Message Title Sebastian Maj created an issue Jenkins / JENKINS-39676 Cannot populate servers via groovy script Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Nov/11 6:12 PM Environment: jenkins-2.19.2-1.1 Active Directory plugin 2.0 Priority: Critical Reporter: Sebastian Maj Using groovy script like this: import jenkins.model.* import hudson.security.* import hudson.plugins.active_directory.* def instance = Jenkins.getInstance() String domain = 'mydomain.com' String site = null String server = 'my_ldap_server' String bindName = null String bindPassword = null adrealm = new ActiveDirectorySecurityRealm(domain, site, bindName, bindPassword, server) instance.setSecurityRealm(adrealm) instance.save() field domain controllers remains empty. This was working in previous version of plugin and it's somehow related to multiple domain support.
[JIRA] (JENKINS-39676) Cannot populate servers via groovy script
Title: Message Title Sebastian Maj updated an issue Jenkins / JENKINS-39676 Cannot populate servers via groovy script Change By: Sebastian Maj Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39675) unclassified method hudson.plugins.git.GitChangeSetList getMsg
Title: Message Title
John McAvey created an issue
Jenkins / JENKINS-39675
unclassified method hudson.plugins.git.GitChangeSetList getMsg
Issue Type:
Bug
Assignee:
Unassigned
Components:
script-security-plugin
Created:
2016/Nov/11 5:22 PM
Environment:
Jenkins v2.25 Workflow-cps-plugin v2.19
Priority:
Major
Reporter:
John McAvey
When attempting to access currentBuild.changeSets information, we receive an unclassified method exception. The following is the code requesting the information:
@NonCPS
java.lang.String getChangeMessage() {
def changes = "Changes: \n";
for (entry in currentBuild.changeSets) {
def changeEntry = java.lang.String.format("\t- %s\n", entry.getMsg());
changes += changeEntry;
}
return changes;
}
And the resulting stack trace is:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method hudson.plugins.git.GitChangeSetList getMsg
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146)
at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall$0.callStatic(Unknown Source)
at
[JIRA] (JENKINS-17267) Git clean or wipeout workspace follows junction on Windows slaves
Title: Message Title pjdarton edited a comment on JENKINS-17267 Re: Git clean or wipeout workspace follows junction on Windows slaves [~jglick] I think that this one has been resolved by JENKINS-29956.FYI advising folks "to not use junctions" isn't viable - you might as well advise folks not to use Windows :-)Windows has hard-coded functionality preventing most people from creating Symbolic Links (you need to be a *non-admin* user who's been granted the right to create symbolic links, or you need to be running "as administrator" with no protection) and so the only remaining option is to use a "directory junction" (which anyone can create) .It's a pain in the ^%$£ but it's the only option for most users on Windows. 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-17267) Git clean or wipeout workspace follows junction on Windows slaves
Title: Message Title pjdarton commented on JENKINS-17267 Re: Git clean or wipeout workspace follows junction on Windows slaves Jesse Glick I think that this one has been resolved by JENKINS-29956. FYI advising folks "to not use junctions" isn't viable - Windows has hard-coded functionality preventing most people from creating Symbolic Links (you need to be a non-admin user who's been granted the right to create symbolic links, or you need to be running "as administrator" with no protection) and so the only option is to use a "directory junction". It's a pain in the ^%$£ but it's the only option for most users on Windows. 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-39490) Kubernetes-plugin 0.9 release not in plugin download repo
Title: Message Title Lachlan Evenson closed an issue as Fixed Jenkins / JENKINS-39490 Kubernetes-plugin 0.9 release not in plugin download repo Change By: Lachlan Evenson Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39490) Kubernetes-plugin 0.9 release not in plugin download repo
Title: Message Title Lachlan Evenson commented on JENKINS-39490 Re: Kubernetes-plugin 0.9 release not in plugin download repo Looks like it's there now. Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25616) Support for coverage.xml generated by Android tools
Title: Message Title Bill Bagdon commented on JENKINS-25616 Re: Support for coverage.xml generated by Android tools still not seeing a way to directly use a generated XML report Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38584) REST API for fetching available steps
Title: Message Title Keith Zantow commented on JENKINS-38584 Re: REST API for fetching available steps I did not add the whitelist in the API at this point, my plan is to add that at the UI level by only implementing specific step editor extensions 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39672 Re: Token-macro PCT issues against 2.91.x Code changed in jenkins User: Alex Earl Path: pom.xml http://jenkins-ci.org/commit/token-macro-plugin/d3e264e20e154defe393c6a6ec96f7c466ceb9d7 Log: Merge pull request #25 from andresrc/JENKINS-39672 JENKINS-39672 Fix PCT issues against 2.19.2 Compare: https://github.com/jenkinsci/token-macro-plugin/compare/e9b416c4b2af...d3e264e20e15 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39672 Re: Token-macro PCT issues against 2.91.x Code changed in jenkins User: Andres Rodriguez Path: pom.xml http://jenkins-ci.org/commit/token-macro-plugin/36a7e5b5310981d243fee0dfd40178dd763dcafa Log: JENKINS-39672 Fix PCT issues against 2.19.2 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Steve Springett commented on JENKINS-38991 Re: NullPointerException in logging of DependencyCheckExecutor Can you try the 1.4.5 SNAPSHOT in the master branch? https://github.com/jenkinsci/dependency-check-plugin/pull/7 should solve 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-39591) Unable to find Role-Based Strategy under Configure Global Security
Title: Message Title Sud Arav updated an issue Jenkins / JENKINS-39591 Unable to find Role-Based Strategy under Configure Global Security Change By: Sud Arav Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build. {{ The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. }} {{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true }}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build. {{ The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. }} {{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true}}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build.The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. {{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true}}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan updated an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Change By:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process.All other files are removed except "version.txt" in which we store a product version number specific to the build.The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number.{{ version.txt #${BUILD_NUMBER}-${ibm.dv.git_branch}- true true true }}I have no concrete evidence or reproduction step I'm afraid, sorry about that.However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-39674) Build name file path file gets locked by Jenkins process
Title: Message Title Toby O'Sullivan commented on JENKINS-39674 Re: Build name file path file gets locked by Jenkins process Additional note: Cleaning the workspace also fails, and trying to delete the workspace on disk is not possible either as Windows reports the version.txt is locked by the java.exe process 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-39674) Build name file path file gets locked by Jenkins process
Title: Message Title
Toby O'Sullivan created an issue
Jenkins / JENKINS-39674
Build name file path file gets locked by Jenkins process
Issue Type:
Bug
Assignee:
Lev Mishin
Components:
build-name-setter-plugin
Created:
2016/Nov/11 3:43 PM
Environment:
Jenkins ver. 1.632 running on Windows 3012 R2 Build-name-setter v 1.5.1
Priority:
Minor
Reporter:
Toby O'Sullivan
Our build intermittently fails when we are trying to clean the workspace because a particular file is locked by the Jenkins java process. All other files are removed except "version.txt" in which we store a product version number specific to the build. The only thing different with this file compared to other build artifacts is that it is used by the build name setter plugin to rename the build based on the product version number. {{ version.txt #$ {BUILD_NUMBER} -$ {ibm.dv.git_branch} - true true true }} I have no concrete evidence or reproduction step I'm afraid, sorry about that. However it might be that there is an obvious issue with file closing so I thought I'd raise it with you
[JIRA] (JENKINS-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Task connections implemented. After discussions among the maintainers we decided to cut the scope and focus on delivering this feature as an MVP. Only code review and possible refactoring improvements left to consider before delivery. 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-38991) NullPointerException in logging of DependencyCheckExecutor
Title: Message Title Stephan Krull reopened an issue @Steve Springett: After installing version 1.4.4 and running the build we still have a failure, see stacktrace 09:24:30 [DependencyCheck] Scanning: /var/lib/jenkins/jobs/AuthServer/workspace/authserver/build/libs/authserver.jar 09:24:31 [DependencyCheck] Analyzing Dependencies 09:26:50 [DependencyCheck] One or more exceptions were thrown while executing Dependency-Check 09:26:50 [DependencyCheck] Exception Caught: java.util.ConcurrentModificationException 09:26:50 ERROR: Build step failed with exception 09:26:50 java.lang.NullPointerException 09:26:50 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckExecutor.performBuild(DependencyCheckExecutor.java:109) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:90) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder$1.call(AbstractDependencyCheckBuilder.java:87) 09:26:50 at hudson.remoting.LocalChannel.call(LocalChannel.java:45) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.AbstractDependencyCheckBuilder.perform(AbstractDependencyCheckBuilder.java:87) 09:26:50 at org.jenkinsci.plugins.DependencyCheck.DependencyCheckBuilder.perform(DependencyCheckBuilder.java:209) 09:26:50 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 09:26:50 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) 09:26:50 at hudson.model.Build$BuildExecution.build(Build.java:205) 09:26:50 at hudson.model.Build$BuildExecution.doRun(Build.java:162) 09:26:50 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) 09:26:50 at hudson.model.Run.execute(Run.java:1720) 09:26:50 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 09:26:50 at hudson.model.ResourceController.execute(ResourceController.java:98) 09:26:50 at hudson.model.Executor.run(Executor.java:404) 09:26:50 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure The NullPointerException still arises from the "for" loop. ec.getExceptions() seems to return null objects. Can you fix this? Jenkins / JENKINS-38991 NullPointerException in logging of DependencyCheckExecutor Change By: Stephan Krull Resolution: Fixed Status: Closed Reopened
[JIRA] (JENKINS-38715) Container instance cannot be empty error
Title: Message Title Nando Sola edited a comment on JENKINS-38715 Re: Container instance cannot be empty error I'm getting the same error when the desired capacity of the autoscaling group is set to zero. Our ideal use case would be that the plugin launched a new EC2 cluster instance before deploying the task. This is useful in terms of not having an idle EC2 instace waiting for tasks. 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-38715) Container instance cannot be empty error
Title: Message Title Nando Sola commented on JENKINS-38715 Re: Container instance cannot be empty error I'm getting the same error when the desired capacity of the autoscaling group is set to zero. Our ideal use case would be that the plugin launched a new EC2 instance before deploying the task. This is useful in terms of not having an idle instace waiting for tasks. 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-39611) ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step
Title: Message Title Jean-Christophe Sirot commented on JENKINS-39611 Re: ansible / ansible-playbook -i option is not supported via a parameter in Jenkins job inside Invoke Ansible build step I reviewed this issue and it does not seems to be a bug but it shows that the field names and documentation have to be improved. The "file path" field when the file radio button is selected accepts a comma separated list of hosts. Note that the host list must not contain spaces (before or after the comma) since the ansible-playbook command seems to consider everything between the commas to be a hostname. Also the "inline content" is used to create an inventory file on the fly and avoid the creation of such a file from a script for instance. 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-39673) View-related CLI commands should also work for views on folder level
Title: Message Title arostfx created an issue Jenkins / JENKINS-39673 View-related CLI commands should also work for views on folder level Issue Type: Improvement Assignee: Unassigned Components: cloudbees-folder-plugin Created: 2016/Nov/11 2:52 PM Priority: Major Reporter: arostfx Jenkins supports a variety of CLI commands for view maintenance: add-job-to-view create-view delete-view get-view remove-job-from-view update-view Currently, those commands cannot be used to manage views that are defined on folder level. For users that rely on automated management of views, this is a major obstacle when introducing folders – they basically need to stop using the CLI commands and resport to custom groovy code for folder maintenance. Therefore, it will be useful to extend the above CLI commands so they also support views that exist on folder level.
[JIRA] (JENKINS-39672) Token-macro PCT issues against 2.91.x
Title: Message Title Andres Rodriguez updated JENKINS-39672 Jenkins / JENKINS-39672 Token-macro PCT issues against 2.91.x Change By: Andres Rodriguez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38920) JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38920 Re: JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifestSpec.groovy src/test/resources/org/jenkinsci/gradle/plugins/jpi/test.mf http://jenkins-ci.org/commit/gradle-jpi-plugin/65547ed4b757b1a476a198c9a5e5d9113be38b80 Log: Merge pull request #81 from daspilker/JENKINS-38920 JENKINS-38920 fixed problem with missing Plugin-Class attribute in generated manifest Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/2acb996a417f...65547ed4b757 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-38920) JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38920 JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned Change By: SCM/JIRA link daemon 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-38920) JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38920 Re: JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifestSpec.groovy src/test/resources/org/jenkinsci/gradle/plugins/jpi/test.mf http://jenkins-ci.org/commit/gradle-jpi-plugin/022c059aba2dd9f4322b4624e03efb696e46b071 Log: fixed problem with missing Plugin-Class attribute in generated manifest [FIXES JENKINS-38920] 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title Andres Rodriguez started work on JENKINS-39672 Change By: Andres Rodriguez 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-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund edited a comment on JENKINS-39668 Re: Attempts to copy files across jobs. Problem seems to have been introduced Nov 9 in a plugin update. Job 971 671 fails, prev job 970 670 is OK, only job relative paths here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/670/warnings27Result/ 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-39672) Token-macro PCT issues against 2.91.x
Title: Message Title Andres Rodriguez created an issue Jenkins / JENKINS-39672 Token-macro PCT issues against 2.91.x Issue Type: Bug Assignee: Andres Rodriguez Components: token-macro-plugin Created: 2016/Nov/11 2:17 PM Environment: Jenkins 2.19.2 Token Macro 2.0 Priority: Minor Reporter: Andres Rodriguez Because of JENKINS-21486 token-macro fail the PCT scenario against 2.19.x. Proposed fix is to bring the needed test dependencies to the POM. Add Comment
[JIRA] (JENKINS-39614) Sort failed jobs first
Title: Message Title Tommy Tynjä resolved as Fixed Jenkins / JENKINS-39614 Sort failed jobs first Change By: Tommy Tynjä 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-39614) Sort failed jobs first
Title: Message Title Tommy Tynjä commented on JENKINS-39614 Re: Sort failed jobs first PR 215 merged: 9dcfe9aae5ee8c70ccdf2302230fcae8b4ac8ab3 Will be part of next release. Thank you Mikael Sundberg for your contribution! 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-39614) Sort failed jobs first
Title: Message Title Tommy Tynjä assigned an issue to Mikael Sundberg Jenkins / JENKINS-39614 Sort failed jobs first Change By: Tommy Tynjä Assignee: Patrik Boström Mikael Sundberg 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-35013) PluginManager not able to update
Title: Message Title Sahil Shaikh commented on JENKINS-35013 Re: PluginManager not able to update I am facing the same issue with Jenkins 2.19.2. java.io.IOException: Could not find JSON in http://updates.jenkins-ci.org/update-center.json?id=default=2.19.2 Jenkins is behind corporate proxy and the HTTP Proxy settings gives "Siccess" on Validate Proxy 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-39571) Jenkins doesn't start after plugin update
Title: Message Title M U commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Please take a look at the following files: support_2016-11-11_12.58.39.zip support_2016-11-11_13.48.03.zip What I did: Created the first bundle Updated some plugins and activated "restart Jenkins after installation" Jenkins tried to restart, but stucks in "Please wait while Jenkins is getting ready to work..." Restarted Jenkins' Windows service Created the second bundle 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-39571) Jenkins doesn't start after plugin update
Title: Message Title M U updated an issue Jenkins / JENKINS-39571 Jenkins doesn't start after plugin update Change By: M U Attachment: support_2016-11-11_12.58.39.zip Attachment: support_2016-11-11_13.48.03.zip 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-39671) PageLoading indicator not working on pipelines page
Title: Message Title Tom FENNELLY created an issue Jenkins / JENKINS-39671 PageLoading indicator not working on pipelines page Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/11 1:58 PM Priority: Major Reporter: Tom FENNELLY The does not seem to be clicking into action on the pipelines page, with the result that the loading indicator just stays in a loading state forever, which looks a bit weird. I had a quick look at it but can't make any sense of it. Maybe someone else can. Seems like PageLoading is not activated on the page at all and so the LoadingIndicator show and hide functions are never called. That's just from a quick scan though, so not really sure. Add Comment
[JIRA] (JENKINS-38937) GitHub API cache is not working
Title: Message Title
Kirill Merkushev edited a comment on JENKINS-38937
Re: GitHub API cache is not working
You can check that cache is used by following steps:1. Click on "Reregister hooks for all jobs"2. Check that there is a folder in cache:{code}$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/796K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/76c844e5800K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/{code}3. Set cache size to 0, then save global config4. Now cache should be cleared:{code}$ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/4.0K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/{code}5. Set cache to any positive num back and resave global config. Then check steps 1-2.Then please write results . Also please provide full list of plugins (maybe some of them eat your limits without using cache from GitHub plugin's client?)
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-38937) GitHub API cache is not working
Title: Message Title Kirill Merkushev commented on JENKINS-38937 Re: GitHub API cache is not working You can check that cache is used by following steps: 1. Click on "Reregister hooks for all jobs" 2. Check that there is a folder in cache: $ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 796K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/76c844e5 800K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 3. Set cache size to 0, then save global config 4. Now cache should be cleared: $ du -h /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 4.0K /opt/jenkins/org.jenkinsci.plugins.github.GitHubPlugin.cache/ 5. Set cache to any positive num back and resave global config. Then check steps 1-2. Then please write results 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-35246) Kubernetes nodes not getting deleted when a pipeline job fails
Title: Message Title Elmar Weber commented on JENKINS-35246 Re: Kubernetes nodes not getting deleted when a pipeline job fails To clarify: The pods are terminated and deleted in kubernetes the jenkins slave reference of them in Jenkins is not deleted when they are terminated and deleted in kubernetes 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-38734) RTC environment variables to set
Title: Message Title Fabian Güttge closed an issue as Fixed Problems vanished after update Jenkins / JENKINS-38734 RTC environment variables to set Change By: Fabian Güttge Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38734) RTC environment variables to set
Title: Message Title Fabian Güttge commented on JENKINS-38734 Re: RTC environment variables to set I updated to Jenkins ver. 2.19.2 Pipeline 2.4 Pipeline: Groovy 2.23 Pipeline: Job 2.9 and this solved the issue for me. I suspect that this issue is connected to JENKINS-30910 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-39571) Jenkins doesn't start after plugin update
Title: Message Title Oleg Nenashev commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Yes, it would be nice 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-39571) Jenkins doesn't start after plugin update
Title: Message Title M U commented on JENKINS-39571 Re: Jenkins doesn't start after plugin update Okay, the plugin is installed. What would be the most helpful workflow for you? Create an initial bundle, do the update of some plugins for enforce the restart problem and create a second bundle afterwards? 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-39670) Jenkins changes workspace layout on 2nd startup
Title: Message Title
Jens Keller created an issue
Jenkins / JENKINS-39670
Jenkins changes workspace layout on 2nd startup
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Nov/11 12:22 PM
Priority:
Major
Reporter:
Jens Keller
Used Jenkins version: 2.19.1, but I'm pretty sure this behavior is also present in older jenkins versions Steps to reproduce:
Download the jenkins.war file
Make sure you have an empty/not existing ~/.jenkins (or whatever JENKINS_HOME directory is used)
From the directory where you downloaded the .war file, run `java -Djenkins.install.runSetupWizard=false -jar jenkins.war`
When Jenkins is started, go to Manage Jenkins -> Configure System and click the "Advanced" button underneath the home directory setting at the top of the page
Observation: the workspace root directory is specified as`$ {JENKINS_HOME}/workspace/${ITEM_FULLNAME}`, as it is documented on https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins - Cancel the process - Restart Jenkins and again, go to the central configuration - Observation: the workspace root directory suddenly changed to `${ITEM_ROOTDIR}/workspace` This behavior is extremely odd and creates a lot of confusion and wastes people's time, as some Jenkins servers/jobs have the one layout, and some have the other layout, depending on when the jobs where created and whether Jenkins was re-started in between or not. Also I want to raise that the documentation is contradicting: - in the built-in documentation of the config option, it says `The default value is ${ITEM_ROOTDIR}/workspace.` - in the above mentioned wiki page it indicates that
[JIRA] (JENKINS-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund edited a comment on JENKINS-39668 Re: Attempts to copy files across jobs. Problem seems to have been introduced Nov 9 in a plugin update. Job 971 fails, prev job 970 is OK, only job relative oaths paths here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/670/warnings27Result/ 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-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund commented on JENKINS-39668 Re: Attempts to copy files across jobs. Problem seems to have been introduced Nov 9 in a plugin update. Job 971 fails, prev job 970 is OK, only job relative oaths here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/670/warnings27Result/ 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-39669) Builds fail when loading jenkins.util.SystemProperties caused by java.lang.NoClassDefFoundError: javax/servlet/ServletContextListener
Title: Message Title Robert Klaus created an issue Jenkins / JENKINS-39669 Builds fail when loading jenkins.util.SystemProperties caused by java.lang.NoClassDefFoundError: javax/servlet/ServletContextListener Issue Type: Bug Assignee: Unassigned Components: core, maven-plugin Created: 2016/Nov/11 11:52 AM Environment: Jenkins 2.19.1, 2.19.2 java.version 1.8.0_112 java.vm.vendor Oracle Corporation java.vm.version 25.112-b15 os.arch amd64 os.name Linux BUILD_TIMESTAMP 2016_1034 Maven 3.3.9 Priority: Blocker Reporter: Robert Klaus We have a similar exception as in JENKINS-35184 but this happens with builds only on master. In the hope that it is fixed we upgraded to 2.19.2 but it didn't help. The exception occurs on a random basis and cannot be pinpointed to a specific build, plugin, time,.. When it happens, all builds after that tend to fail as well. We currently have to do a restart of Jenkins on a daily basis and sometimes multiple times. Restarting Jenkins is the only workaround we currently have and is growing into a pain especially when we are releasing. This issue is a blocker for us. Our setup is: one master Jenkins running mostly all builds one Windows slave for running selenium tests most builds are run with Maven using the Maven Project Type job (seems to be important) StackTrace from the build logs:
[JIRA] (JENKINS-39619) TFS plugin doesn't check out code writable
Title: Message Title Righardt Marais updated an issue Jenkins / JENKINS-39619 TFS plugin doesn't check out code writable Change By: Righardt Marais We have an issue where we copy files when we build as pre/post build process. The new version of Jenkins and the tfs version 5.2.1 does nto not leave workspace writable files in the workspace . Thus copy processes that overwrite files fail.The older Jenkins and TFS 3.2.0 did do this and all our build processes worked.Can the ability to select writable or not checkbox be added fro for us who need it? Otherwise we need to go fiddle with Attrib statements after Code get action. 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-34040) Add support for Pipeline plugin in the Delivery Pipeline plugin
Title: Message Title Tommy Tynjä commented on JENKINS-34040 Re: Add support for Pipeline plugin in the Delivery Pipeline plugin Moving tasks out of scope for this ticket. See if a meta task connection can be added between stages. 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-39668) Attempts to copy files across jobs.
Title: Message Title Anders Hoglund created an issue Jenkins / JENKINS-39668 Attempts to copy files across jobs. Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2016/Nov/11 11:34 AM Environment: Ubuntu 16.04LTS Priority: Major Reporter: Anders Hoglund The warnings-plugin seems to access files and tries to make copies accross job boundries. Noticed this when new files pulled in one job are not yet available in the other, then I get a lot of false warnings added to the statistics. The current job name is "BorisB_BetaFlight" and from there the warnings-plugin tries to access files in a job named "AndWho_Betaflight_buildsystem" See it all here: http://andwho.sytes.net:8080/job/BorisB_BetaFlight/697/warnings27Result/source.-8247652556134220142/#16 01 Copying the source file '/var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' from the workspace to the build folder 'f16d8a0.tmp' on the Jenkins master failed. 02 Is the file '/var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' a valid filename? 03 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]//var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' 04 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace//var/lib/jenkins/jobs/AndWho_Betaflight_buildsystem/workspace/src/test/./src/main/target/KAKUTEF4-V1/target.c' 05
[JIRA] (JENKINS-39667) PIpeline job ignores custom workspace location
Title: Message Title
Dmitriy Belyaev created an issue
Jenkins / JENKINS-39667
PIpeline job ignores custom workspace location
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Nov/11 11:34 AM
Environment:
Windows 7, x64 Jenkins 2.19.2 Pipeline 2.4
Priority:
Major
Reporter:
Dmitriy Belyaev
After last update (not sure which one, everything worked last time on 4. nov 2016) pipeline job began to use local jenkins directory (c:/Users/jenkins/.jenkins) for workspaces completely ignoring settings set under: "Manage Jenkins / Worspace Root DIrectory" and "Manage Jenkins / Build Record Root Directory", which are configured as follow: Workspace Root Directory = d:/jenkins/ws/$ {ITEM_FULLNAME}/work Build Record Root Directory = d:/jenkins/ws/${ITEM_FULLNAME} /builds
Add Comment
[JIRA] (JENKINS-39589) Default pod settings in 0.9 make no sens
Title: Message Title
Carlos Sanchez commented on JENKINS-39589
Re: Default pod settings in 0.9 make no sens
It shouldn't have changed, and specifically the jnpl container should have
${computer.jnlpmac} ${computer.name}
as args https://github.com/carlossg/jenkins-kubernetes-plugin/issues/7
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-39589) Default pod settings in 0.9 are wrong
Title: Message Title Carlos Sanchez updated an issue Jenkins / JENKINS-39589 Default pod settings in 0.9 are wrong Change By: Carlos Sanchez Summary: Default pod settings in 0.9 make no sens are wrong 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-39665) Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin
Title: Message Title Java Dev updated an issue Jenkins / JENKINS-39665 Unnecessary Scrollbars on build with parameters screen when using Active Choices Plugin Change By: Java Dev Environment: - Operating System: Ubuntu Server 14.04 LTS 64Bit- Jenkins Version: 2.20- Active Choices Plugin version: 1.40- Java(TM) SE Runtime Environment: (build 1.8.0_101-b13)- Not run in a container.- Debian install- Firefox 49.0.2- Chrome Version 54.0.2840.71 (64-bit) 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.
