[JIRA] (JENKINS-37604) API to get link to branch on Github
Title: Message Title James Dumay updated JENKINS-37604 Jenkins / JENKINS-37604 API to get link to branch on Github Change By: James Dumay 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-37604) API to get link to branch on Github
Title: Message Title James Dumay started work on JENKINS-37604 Change By: James Dumay 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-37604) API to get link to branch on Github
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37604 API to get link to branch on Github Change By: James Dumay Sprint: 1.0-beta-1, pacific, 1.0-b05/b-06, release candidate tethys Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37604) API to get link to branch on Github
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-37604 API to get link to branch on Github Change By: James Dumay Assignee: Ivan Meredith 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-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title James Dumay commented on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly Vivek Pandey if we have to synthesise a stage I am happy with it being called "Parallel". Would it be possible to attach some data to the synthesised node so that we can show a warning in the UI about how it has been transformed? I'd like to educate users more about the usage of Stage. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39179) All builds hang, JNA load deadlock on Windows slave
Title: Message Title Greg Smith commented on JENKINS-39179 Re: All builds hang, JNA load deadlock on Windows slave I upgraded to 2.32.1 – and the problem still exists in that version. I had a build lockup within the first few hours. But I also upgraded to the latest vcenter plugin: And the latest version has the option to specify Advanced options, meaning I could actually apply the "-Dhudson.remoting.RemoteClassLoader.force=com.sun.jna.Native" workaround to my dynamically created slaves. I will report back if there is a lock up again with this system property applied. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38381) Optimize log handling in Pipeline and Durable Task
Title: Message Title Jesse Glick commented on JENKINS-38381 Re: Optimize log handling in Pipeline and Durable Task Did some optimizations; down to: Took 2525ms to run the build Took 761ms to write HTML of whole build Took 133ms to compute length of whole build Took 86ms to write truncated HTML of whole build Took 111ms to write plain text of whole build Took 379ms to write HTML of one node Took 57ms to compute length of one node Took 64ms to write truncated HTML of one node Took 62ms to write plain text of one node Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40874) Missing ErrorAction after Jenkins restart
Title: Message Title
Vivek Pandey created an issue
Jenkins / JENKINS-40874
Missing ErrorAction after Jenkins restart
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2017-01-06-16-35-47-046.png, image-2017-01-06-16-36-37-585.png, image-2017-01-06-16-37-41-271.png, image-2017-01-06-16-38-05-125.png
Components:
workflow-api-plugin, workflow-basic-steps-plugin
Created:
2017/Jan/07 12:39 AM
Priority:
Major
Reporter:
Vivek Pandey
On Jenkins restart FlowNode corresponding to ErrorStep has missing ErrorAction. I tried this script:
node {
stage('stage1') {
sh "echo 42"
error("this error should appear in log")
}
}
On executing this script, FlowNode corresponding to error step has ErrorAction. The error message "this error should appear in log" can be seen by hovering over stage view UI. After restart, error step flow node has no such ErrorAction, try hovering over stage view UI and it won't show the error message. Persisted XML file for that error step seems to have correct ErrorAction with error message and stack trace but somehow its not de-serialized. There seems to be problem in general, take a look at https://github.com/jenkinsci/blueocean-plugin/commit/213854399c924919b7afb7160819a7f0b892dd19, here ExplodingStep has both ErrorAction and LogAction, but they are missing after jenkins restart. We are trying to capture failing step's error messages and show them in blueocean UI, it breaks the behavior on jenkins restart. After executing
[JIRA] (JENKINS-40447) PublishHTMLStepExecution.run can block CPS thread
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40447 Re: PublishHTMLStepExecution.run can block CPS thread Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/htmlpublisher/HtmlPublisher.java src/main/java/htmlpublisher/HtmlPublisherTarget.java src/main/java/htmlpublisher/workflow/PublishHTMLStepExecution.java src/main/resources/htmlpublisher/HtmlPublisher/config.jelly src/main/resources/htmlpublisher/HtmlPublisherTarget/HTMLAction/sidepanel.jelly src/main/resources/htmlpublisher/HtmlPublisherTarget/HTMLBuildAction/sidepanel.jelly src/main/resources/index.jelly http://jenkins-ci.org/commit/htmlpublisher-plugin/f2a4519bc47a4b1f9cedc37affb9d5be65122213 Log: [FIXED JENKINS-40447] Use AbstractSynchronousNonBlockingStepExecution, which requires updating to 1.609.x. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40803) Endless Loop when "provisoning config files..." when run from a build promotion
Title: Message Title Daniel Beck commented on JENKINS-40803 Re: Endless Loop when "provisoning config files..." when run from a build promotion Promoted Builds plugin is a giant mess because of situations like this. It's design is less than great and pretty infamous by now actually There are a few limitations in the core APIs (IIRC no sane way to add a collection of items to something that's not an ItemGroup already), which kind of facilitated this mess, but none of them are really related to the Folders plugin (??). In this specific case you should be able to add an extra check whether the item you get is a JobProperty, and if so, continue with its owner. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40873) Recent change to content-type support breaks default text/plain
Title: Message Title Richard Lee created an issue Jenkins / JENKINS-40873 Recent change to content-type support breaks default text/plain Issue Type: New Feature Assignee: Janario Oliveira Components: http-request-plugin Created: 2017/Jan/06 11:52 PM Priority: Minor Reporter: Richard Lee I believe that this change https://github.com/jenkinsci/http-request-plugin/commit/8620e917855676506c85d2882a53192191bce6c2 broke support for not setting the contentType in an httpRequest. Previously, it would not pass any contentType parameter to StringEntity, which meant to use 'text/plain'. Now, I believe if you don't explicitly set the contentType, it passes the value of NOT_SET (which is "") to StringEntity, which then perhaps does something weird and causes requests to fail. I have working code that, at some version prior to 1.8.13, worked, and with 1.8.13 does not work. Adding an explicit contentType: 'TEXT_PLAIN' to my httpRequest command causes it to work again. Add Comment
[JIRA] (JENKINS-40872) An unauthenticated request to / should use a HTTP level redirect
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-40872 An unauthenticated request to / should use a HTTP level redirect Issue Type: Improvement Assignee: Unassigned Components: core Created: 2017/Jan/06 11:50 PM Environment: Jenkins 2.39 Priority: Minor Reporter: R. Tyler Croy The root URL in Jenkins apparently uses HTML-based redirects and returns a 403 when accessing the root URL. Aside from being confusing, this seems like borderline incorrect. This should probably be an HTTP 307 "Temporary Redirect" instead. % curl -Lv http://localhost:8081/ > /dev/null * Hostname was NOT found in DNS cache % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying ::1... * Connected to localhost (::1) port 8081 (#0) > GET / HTTP/1.1 > User-Agent: curl/7.38.0 > Host: localhost:8081 > Accept: */* > < HTTP/1.1 403 Forbidden < Date: Fri, 06 Jan 2017 23:47:28 GMT < X-Content-Type-Options: nosniff < Set-Cookie: JSESSIONID.fe7d94cf=1q9kqfkzeob2razyebu1nxxzy;Path=/;HttpOnly < Expires: Thu, 01 Jan 1970 00:00:00 GMT < Content-Type: text/html;charset=UTF-8 < X-Hudson: 1.395 < X-Jenkins: 2.39 < X-Jenkins-Session: 24a8feb9 < X-You-Are-Authenticated-As: anonymous < X-You-Are-In-Group: < X-Required-Permission: hudson.model.Hudson.Read < X-Permission-Implied-By: hudson.security.Permission.GenericRead < X-Permission-Implied-By: hudson.model.Hudson.Administer < Content-Length: 793 *
[JIRA] (JENKINS-40797) Job DSL Custom config file with name not found
Title: Message Title Daniel Spilker closed an issue as Fixed Jenkins / JENKINS-40797 Job DSL Custom config file with name not found Change By: Daniel Spilker Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38874) Shorten branch's folder name
Title: Message Title John Smith commented on JENKINS-38874 Re: Shorten branch's folder name I submitted a pull request at https://github.com/jenkinsci/branch-api-plugin/pull/62 that fixes this problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40871) Running Pipeline Status with Milestone/Locks Needs Better visualization
Title: Message Title Alejandro del Castillo created an issue Jenkins / JENKINS-40871 Running Pipeline Status with Milestone/Locks Needs Better visualization Issue Type: Improvement Assignee: Unassigned Attachments: batch_pipeline.jpg Components: blueocean-plugin Created: 2017/Jan/06 10:01 PM Priority: Major Reporter: Alejandro del Castillo It is a common practice to batch changes in a pipeline via milestone/lock [1]. That way, resources are more efficiently used since there is only one instance of each stage running at a time. In practice, the milestone step aborts any instance of a pipeline if another pipeline instance, with new commits on it, reaches the milestone point. Currently, blue-ocean shows the steps that run on the pipeline in green, then the ones that didn't run on that instance (since a newer one hit the milestone) are rendered as grey. Users that need to track where in the pipeline their change is need to close their pipeline instance page, then manually look for the first non-aborted pipeline instance after. Ideally, Jenkins should provide a better way to track where the change is. Maybe show the pipeline stages that are running on a different instance (due to a milestone) in grey, but as running? Some other way? [1] https://jenkins.io/blog/2016/10/16/stage-lock-milestone/
[JIRA] (JENKINS-24837) Viewing In Progress Status for "external-monitor-job"
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-24837 Viewing In Progress Status for "external-monitor-job" Jenkins accepts a notification if and when the task completes, but currently there is no system for indicating that a task has started and to stand by. Change By: Jesse Glick Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40849) Script security should whitelist Result classes
Title: Message Title Jesse Glick commented on JENKINS-40849 Re: Script security should whitelist Result classes Fine so far as it goes, but useless without JENKINS-34464. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40870) Delay by parent job to report the child’s job completion.
Title: Message Title Dilip Mahadevappa created an issue Jenkins / JENKINS-40870 Delay by parent job to report the child’s job completion. Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: matrix-project-plugin Created: 2017/Jan/06 8:56 PM Environment: Jenkins LTS 1.642.3 Matrix Project Plugin 1.6 Labels: matrix consoleoutput Priority: Major Reporter: Dilip Mahadevappa Hi, We see a significant delay by parent job to report the child’s job completion. Example console output of parent job: Parent-1 job's console log: 04:43:52 Completed Parent-1 » Child-50 SUCCESS . . 04:44:15 Completed Parent-1 » Child-60 SUCCESS . . Child-50 job's console log: . . 04:37:04 Finished: SUCCESS Child-60 job's console log: . . 04:35:14 Finished: SUCCESS
[JIRA] (JENKINS-40268) Can not read Environment variables `NVM_NODEJS_ORG_MIRROR`
Title: Message Title Tomas Salazar started work on JENKINS-40268 Change By: Tomas Salazar 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-40869) Allow for unescaped XML in test detail output
Title: Message Title Tim Drury created an issue Jenkins / JENKINS-40869 Allow for unescaped XML in test detail output Issue Type: New Feature Assignee: Unassigned Attachments: 2017-01-06_15-13-22.png Components: junit-plugin Created: 2017/Jan/06 8:18 PM Environment: Jenkins 1.596.1 junit-plugin 1.8 on SUSE Linux Priority: Major Reporter: Tim Drury We run SoapUI integration tests in a jenkins job. SoapUI creates the test results in junit XML format. The details of each test includes the XML request and response SoapUI. In Jenkins, when expanding a test element in the UI, the details are shown with the XML escaped making it very hard to quickly identify issues. I've attached a screenshot as an example I'm ok with the escaping of the html which can be seen near the top, but the escaping of the '<' and '>' and single quotes makes the XML very difficult to follow. Is it possible to add an option to NOT escape the XML special characters (<,>,')?
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally I uploaded it to my test jenkins instance. will let you know if we see the problem again. Thank you very much for your time and efforts. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18862) Add an ability to specify external GIT repository for scripts
Title: Message Title Ed Mangual commented on JENKINS-18862 Re: Add an ability to specify external GIT repository for scripts That is correct. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title Andrew Bayer commented on JENKINS-40370 Re: Run stage when branch name matches PR is up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/78 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title Andrew Bayer started work on JENKINS-40370 Change By: Andrew Bayer 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-40370) Run stage when branch name matches
Title: Message Title Andrew Bayer updated JENKINS-40370 Jenkins / JENKINS-40370 Run stage when branch name matches Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40657) can not create instances of utilities from a shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40657 Re: can not create instances of utilities from a shared libraries Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/resources/libraryObjectInScript.groovy pipeline-model-definition/src/test/resources/libraryObjectOutsideScript.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/3dfbc37c0f28a52ef0bf548385b5825d25011ceb Log: Merge pull request #81 from abayer/jenkins-40657 JENKINS-40657 Verify that library objects can be instantiated Compare: https://github.com/jenkinsci/pipeline-model-definition-plugin/compare/85b800518475...3dfbc37c0f28 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40657) can not create instances of utilities from a shared libraries
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40657 Re: can not create instances of utilities from a shared libraries Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/resources/libraryObjectInScript.groovy pipeline-model-definition/src/test/resources/libraryObjectOutsideScript.groovy http://jenkins-ci.org/commit/pipeline-model-definition-plugin/2d00c2e7561acaae715301b56703218a52430b01 Log: JENKINS-40657 Tests trying to reproduce the issue They don't reproduce the issue, of course. Other than the need for org.foo.Zot to be Serializable, that is. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40657) can not create instances of utilities from a shared libraries
Title: Message Title Andrew Bayer updated JENKINS-40657 Jenkins / JENKINS-40657 can not create instances of utilities from a shared libraries Change By: Andrew Bayer Status: In Review Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally got it to build! now to install 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-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title Steve Ramage commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally Sadly I'm not a Maven expert, or even a Jenkins one, I just had to fix this issue a year and a bit ago, and had forgotten about this until this morning when I got an e-mail from this ticket The only thing I can recommend is maybe try: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-CreatingaNewPlugin or if you want and would trust it I would offer to send you the build I made. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally this is actually at the top of the output. [INFO] Scanning for projects... [WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:1.95 is missing, no dependency information available [WARNING] Failed to build parent project for org.jenkins-ci.plugins:Parameterize d-Remote-Trigger:hpi:2.2.1-SNAPSHOT [INFO] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40868) Support explicit invocation of destroy command
Title: Message Title Chad La Joie created an issue Jenkins / JENKINS-40868 Support explicit invocation of destroy command Issue Type: New Feature Assignee: David Pires Components: terraform-plugin Created: 2017/Jan/06 6:55 PM Priority: Minor Reporter: Chad La Joie I would like to be able to directly invoke the TF destroy command. As noted in JENKINS-40867 I've created a build-a-cluster TF plan. I have a Jenkins job that lets a developer spin up a cluster when they need it. I'd like to expose a way for them to destroy that cluster when they're done. This could either be a separate job (which pretty much requires JENKINS-40867 so that the two jobs could share TF files) or allow the TF command used to be determined by a job parameter. Add Comment
[JIRA] (JENKINS-40867) Allow Terraform files to be written to a workspace subdirectory
Title: Message Title Chad La Joie created an issue Jenkins / JENKINS-40867 Allow Terraform files to be written to a workspace subdirectory Issue Type: New Feature Assignee: David Pires Components: terraform-plugin Created: 2017/Jan/06 6:48 PM Priority: Minor Reporter: Chad La Joie I've created a generic "build a cluster" Terraform plan and I'd like to build a generic Jenkins job as well. But I can't right now. Assume that developer A wants to come in and run the "build a cluster" job and create Cluster-A. Then assume developer B wants to do the same thing and create Cluster-B. Today, trying to do this with a single job will cause Cluster-A to be destroyed and Cluster-B created. So, my ask is to provide an option that specifies into which directory the TF state and variable files are written. If I had that, I could create a parameterized Jenkins job where one parameter was the cluster id. Then I could use that parameter as part of the directory path for the TF files. The TF files for Cluster-A would then be separate from those of Cluster-B. Add Comment
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.029 s [INFO] Finished at: 2017-01-06T13:13:29-05:00 [INFO] Final Memory: 13M/32M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2. 5:compile (default-compile) on project Parameterized-Remote-Trigger: Fatal error compiling: tools.jar not found: C:\Program Files (x86)\Java\jre1.8.0_45\..\lib\ tools.jar -> [Help 1] [ERROR] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40823) pipeline job isn't triggered when initiated by startup trigger
Title: Message Title Emory Penney started work on JENKINS-40823 Change By: Emory Penney 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-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally ty making 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-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title Vivek Pandey commented on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly James Dumay I will start with what I think is work involved or issues we need to solve and then make determination: This virtual stage would collate all orphan (with no parent stage) consecutive top level parallels (with no stages in between) What would be the display name or label of each virtual stage? Current implementation is event based parsing API (bismuth), it sends events for all nodes. For stage it sends events that help compute stages, status, timing info etc. * Computation of stage would require copying/collating status from underlying parallel * Computation of timing will involve capture timing from underlying parallel blocks. This might be incorrect unless we capture all out-of-stage nodes (steps as well) and then compute timing info (duration, start and end) Sythentic stage id generation. node id is generated during execution, its simple integer. I am hoping CpsFlowExecution.iota() might just do it but maybe there are edge cases where there are chances of id conflict - like pipeline is midway execution so id of synthetic stage could be reused later? Or we generate UUID for these nodes ourselves? Sam Van Oort are there other complications it might cause or better approach to handle it? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title Steve Ramage commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally I think just be in the top level directory with the pom.xml file, run the command and then look in the build or output directory. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36952) vSphere-cloud-plugin VSPHERE_IP NULL on clone from template via pipeline plugin
Title: Message Title Jonathan Bland commented on JENKINS-36952 Re: vSphere-cloud-plugin VSPHERE_IP NULL on clone from template via pipeline plugin Still experiencing this issue. ESXi 5.5 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40273) NPE when trying to delete a job with p4 configured
Title: Message Title Paul Allen started work on JENKINS-40273 Change By: Paul Allen 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-40273) NPE when trying to delete a job with p4 configured
Title: Message Title Paul Allen commented on JENKINS-40273 Re: NPE when trying to delete a job with p4 configured When you delete the Jenkins Job there are options to allow cleanup and attempt to delete not only the Jenkins Workspace, but also the Perforce client and associated metadata. It seems that the Perforce Credential used to define this Job has been deleted and Jenkins is not able to connection to Perforce to delete the client workspace. This is a bug as I need to check the connection is valid before trying to cleanup. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally got maven.. but have never used it. do I need anything more than the command you gave me? it doesn't seem to be doing anything do I need to tell it what to build or just be in the top level directory with the pom.xml file? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40866) docker.inside() like syntax that keeps the workspace
Title: Message Title
Tom Larrow created an issue
Jenkins / JENKINS-40866
docker.inside() like syntax that keeps the workspace
Issue Type:
Improvement
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2017/Jan/06 5:24 PM
Priority:
Minor
Reporter:
Tom Larrow
With the traditional pipeline we have been able to do a mixture of working with the Jenkins workspace and using docker.inside() to pull in docker containers which have additional build tools needed to do a build. Docker.inside() maps the jenkins workspace to docker volume, so that what happens inside the docker container can read from, and write to the jenkins workspace. Part of this is our build environment. The builds all run from slaves which run as docker containers inside Kubernetes. Those pods run privileged, so that they can reach the docker socket on the host to spin up "peer" docker containers when the docker.inside() commands are run. This is needed in order to run docker commands and to build new docker containers. So for instance a slave does a checkout scm. gathers information about the repository commit using git commands, then does docker.inside() to pull in a pre-configured docker image with all the necessary npm modules already installed. It runs the gulp tasks inside() the container which thanks to the way things are mapped, writes the gulp output back to the jenkins workpace. Then the inside() block closes, and the next steps of the pipeline do a docker build, and docker push to our registry. I initially tired doing this in declarative pipeline by using an agent statement at the top just inside the pipeline{ agent label:'swarm', docker:'our-registry/npm-build:latest' This initially failed because while the slave has git on it, git does not exist inside that npm-build image, so I couldn't use the git commands to determine the url and git commit hash I initially added git to that image, and that part worked, but then I realized I could go no further, since there was no way
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally all the maven downloads I try are failing!! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40454) P4Groovy does not support commas
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-40454
Re: P4Groovy does not support commas
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/groovy/P4Groovy.java http://jenkins-ci.org/commit/p4-plugin/d602135b3620ba2d712ebe494900587f2a0cd3e9 Log: P4Groovy can take variable args or one string for run. A string for simple commands (that don't use a comma): def changes = p4.run("changes", "//...@$ {A}, -s, submitted") Or more complex commands use variable args: def changes = p4.run("changes", "//...@${A} ,$ {B} ", "-s submitted", "-m4") Uses the same rules as P4Python/P4Perl/P4Ruby by keep arg groups together ("-flag "). JENKINS-40454
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title Jesse Glick reopened an issue Jenkins / JENKINS-40113 sematic-versioning-plugin causes dashboard to biff Change By: Jesse Glick Resolution: Fixed 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 more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title Jesse Glick updated JENKINS-40113 Jenkins / JENKINS-40113 sematic-versioning-plugin causes dashboard to biff Change By: Jesse Glick 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-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title Jesse Glick started work on JENKINS-40113 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title Jesse Glick assigned an issue to Stephen Connolly Jenkins / JENKINS-40113 sematic-versioning-plugin causes dashboard to biff Change By: Jesse Glick Assignee: Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title Jesse Glick updated JENKINS-40113 Jenkins / JENKINS-40113 sematic-versioning-plugin causes dashboard to biff Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title Steve Ramage commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally Ugh, for some reason the unit tests are failing on my machine, even if I delete every test. The repository for my fix is here: https://github.com/SJrX/parameterized-remote-trigger-plugin/commits/build-finding, and the branch is build-finding. If you download it, and run mvn -Dmaven.test.skip=true install it should produce a jar and hpi file, I think the hpi file is what you install manually. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-40113 sematic-versioning-plugin causes dashboard to biff 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-40113) sematic-versioning-plugin causes dashboard to biff
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40113 Re: sematic-versioning-plugin causes dashboard to biff Code changed in jenkins User: Stephen Connolly Path: src/main/java/org/jenkinsci/plugins/SemanticVersioning/SemanticVersionColumn.java http://jenkins-ci.org/commit/semantic-versioning-plugin/3ab89b6af9ddfdbc45bd3878094e13fdf5719705 Log: [FIXED JENKINS-40113] sematic-versioning-plugin causes dashboard to biff Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40524) Rework agent syntax to be more extensible
Title: Message Title Patrick Wolf commented on JENKINS-40524 Re: Rework agent syntax to be more extensible Crap. We've changed it again. I already documented the previous way and it is going to print. Let me know the final syntax so I can stop the cards being printed, Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37993) Can't load main dashboard - hudson model view
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-37993 Can't load main dashboard - hudson model view Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37993) Can't load main dashboard - hudson model view
Title: Message Title Jesse Glick reopened an issue Not “fixed”. Jenkins / JENKINS-37993 Can't load main dashboard - hudson model view Change By: Jesse Glick Resolution: Fixed 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 more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally we want the fix anyway we can get 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-40865) Org folders do not encode child project names
Title: Message Title Stephen Connolly updated JENKINS-40865 Jenkins / JENKINS-40865 Org folders do not encode child project names Change By: Stephen Connolly 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-40865) Org folders do not encode child project names
Title: Message Title Stephen Connolly started work on JENKINS-40865 Change By: Stephen Connolly 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-40865) Org folders do not encode child project names
Title: Message Title Stephen Connolly commented on JENKINS-40865 Re: Org folders do not encode child project names Discovered the lack of encoding here while writing tests to verify that JENKINS-40441 is not branch api's problem Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40865) Org folders do not encode child project names
Title: Message Title Stephen Connolly created an issue Jenkins / JENKINS-40865 Org folders do not encode child project names Issue Type: Bug Assignee: Stephen Connolly Components: branch-api-plugin Created: 2017/Jan/06 4:32 PM Priority: Major Reporter: Stephen Connolly The multibranch projects encode the branch project names in the event that the branch name contains invalid characters. This does not happen for org folders Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40863) Shell task ClassNotFoundException: javax.servlet.ServletException
Title: Message Title Jesse Glick started work on JENKINS-40863 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39842) Open Blue Ocean button should not try to load /activity for a folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39842 Re: Open Blue Ocean button should not try to load /activity for a folder Code changed in jenkins User: Tom Fennelly Path: src/main/js/page_objects/classic_jenkins/classicGeneral.js src/test/js/edgeCases/folder.js src/test/js/multibranch/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/1ea16a7e6dc7f9063fb0f96953049e9133c89123 Log: [FIX JENKINS-39842] Open Blue Ocean button should not try to load /activity for a folder (#96) Test for JENKINS-39842 Clicking on the "Open Blue Ocean" button while in a classic folder that's not a MBP project folder should bring the user to the main top-level blue ocean page i.e. pipelines Another test for JENKINS-39842 for @kzantow Using folder and job/branch names that are not confusing (special chars etc). BTW I'm leaving the original tests that were using weird chars because I think it's good to have tests that challenge the url encoding etc. Sure that can result in the presence of weird chars, but weird chars are a fact of life, so good to test against them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-40863) Shell task ClassNotFoundException: javax.servlet.ServletException
Title: Message Title Jesse Glick updated JENKINS-40863 Jenkins / JENKINS-40863 Shell task ClassNotFoundException: javax.servlet.ServletException Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40441) Encoding failure: multibranch fails indexing on ATH for strange pipeline names
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40441 Re: Encoding failure: multibranch fails indexing on ATH for strange pipeline names Code changed in jenkins User: Stephen Connolly Path: src/test/java/integration/BrandingTest.java http://jenkins-ci.org/commit/branch-api-plugin/26505ade48353f6ebffdba3d36af04a569096e55 Log: Check that JENKINS-40441 is not our problem Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java http://jenkins-ci.org/commit/parallels-desktop-plugin/a7fa6d0ac38951c681a3173958e42eae03ead34a Log: CPU and RAM resource limiting implementation Here's general algorithm done for CPU counting and RAM separately: 0. take available CPU cores and physical RAM on host; 1. for each running VM sum virtual CPUs and RAM (main memory and video RAM); 2. add for each VM RAM 500 Mb as virtualization overhead; 3. subtract 1 Gb from host available RAM – consider this to be taken by host OS, apps, Jenkins' java etc. 4. so available resources are: host CPUs minus sum of runnings virtual CPs, host RAM minus all VMs RAM; 5. compare available resources with start VM required resources, if CPU or RAM exceeds available values – refuse to start VM. Bug #JENKINS-40685 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java http://jenkins-ci.org/commit/parallels-desktop-plugin/05019eb06145ff74d24352141c2acb31fb5192d5 Log: Stub to check resource limits before VM start We need to check resource limits (CPU and RAM for now as main resources) before VM start to avoid host overload. Otherwise in case of CPU or memroy overcommit host performance may degrade significantly, even to the state of unresponsibility. Yes, Parallels Desktop internally checks some limits before VM start, but: 0. these checks are not strict (this is bug or not – I don't know); 1. for plugin these checks blocking looks like common VM start failure. So its better to distinguish resources checks issues with others to better handle such errors. Actual implementation goes in the next commit. Bug #JENKINS-40685 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java http://jenkins-ci.org/commit/parallels-desktop-plugin/b714f4cb3e3c09d068389dcd8ee107e2a1bec0ac Log: Proper support of prlctl execution errors At this point we didn't know if prlctl commant finished with sucess or or not, we just parsed its output. To improve error handling, particularly in case of resources exceeding cases, let's throw and catch appropriate exception if prlctl return code is not zero. Bug #JENKINS-40685 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopCloud.java src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java http://jenkins-ci.org/commit/parallels-desktop-plugin/7209020af45ba38320fb3fe6a2d9a1c37bc88008 Log: Yet another attempt to fix VM start-up Foundation stone of this procedure is proper errors handling. Previous attemt did not fix anything in fact. So that if, for example, Jenkins fails to connect to VM through SSH appropriate node stalls in offline mode with job handing on it. Bug #JENKINS-40685 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java src/main/java/com/parallels/desktopcloud/ParallelsDesktopVM.java http://jenkins-ci.org/commit/parallels-desktop-plugin/274d0a5690ffe3c9fa3995c4fbccc548aa659499 Log: Start VM only if it not running already To fix bug with proper limiting the number of VMs runnings on one host we need to rework VM start-up procesdure so that actual virtual machine start will be attempted only if it is not running already (if VM is already running on host no additional limiting could be applied to it). Bug #JENKINS-40685 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopCloud.java src/main/java/com/parallels/desktopcloud/ParallelsDesktopConnectorSlaveComputer.java http://jenkins-ci.org/commit/parallels-desktop-plugin/d00b3b6bd95282ba7ee32b64c82af1797257558e Log: Restore checking for VM existence Check for VM existence was implemented disfunctional in initial commit. Let's reimplement it. Bug #JENKINS-40685 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40685) Operation timed out when launching VM slave
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40685 Re: Operation timed out when launching VM slave Code changed in jenkins User: Roman Kulikov Path: src/main/java/com/parallels/desktopcloud/ParallelsDesktopCloudRetentionStrategy.java http://jenkins-ci.org/commit/parallels-desktop-plugin/4fcdd4ada4172f9ad422656cead2dec245383bc0 Log: Fix left offline VM nodes If VM slave node fails to start for some reason it will be left offline by Jenkins because we just skip check in retention strategy in such case for unclear reason. Bug #JENKINS-40685 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally the master on the server which is kicking off the build on the remote jenkins is windows. the remote jenkins is centos but both are running the latest jenkins version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18862) Add an ability to specify external GIT repository for scripts
Title: Message Title Dominik Bartholdi commented on JENKINS-18862 Re: Add an ability to specify external GIT repository for scripts just to be clear, you would like to have an inhouse catalog (1) - a list of scripts that can be imported into individual jenkins instances via scriptler? (1) https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin#ScriptlerPlugin-Catalogs Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally I am running the latest version of jenkins. the master is centos. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title Steve Ramage commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally I don't know about a different plugin. I did write a fix that works with newer versions and that is what we have been using for 18 months. I just couldn't release it and patch it because it wasn't a perfect fix. Are you familiar with using maven? Another option is I can see what the Jenkins channel says about just changing the minimum supported version. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40863) Shell task ClassNotFoundException: javax.servlet.ServletException
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-40863 Shell task ClassNotFoundException: javax.servlet.ServletException Change By: Kanstantsin Shautsou Environment: 1.642.4 master jvm: osx 10.12; oracle 1.8u112slave: 4.8.15-moby; CentOS Linux release 7.2.1511; openjdk version "1.8.0_71" Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40687) "Automatic Cleanup and Sync" does not delete non-versioned folders, only files
Title: Message Title Paul Allen commented on JENKINS-40687 Re: "Automatic Cleanup and Sync" does not delete non-versioned folders, only files The AutoCleanImpl only cleans up Versioned files. In addition Perforce will not remove empty directories unless you set the RMDIR option in your workspace, and then only if Perforce removes the last file (so if it was already empty, Perforce will not delete it). workspace: [$class: 'ManualWorkspaceImpl', ... spec: [rmdir: true, ... The 'p4cleanup' is a bit more drastic, deleting the client workspace. Do check the Global cleanup options under 'Manage Jenkins' -> 'Configure System' as you can set it to remove all content and client metadata. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39842) Open Blue Ocean button should not try to load /activity for a folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39842 Re: Open Blue Ocean button should not try to load /activity for a folder Code changed in jenkins User: tfennelly Path: src/test/js/edgeCases/folder.js src/test/js/multibranch/folder.js http://jenkins-ci.org/commit/blueocean-acceptance-test/a5a3fd7171edc614fbba387fd5b0af5ea78faae3 Log: Another test for JENKINS-39842 for @kzantow Using folder and job/branch names that are not confusing (special chars etc). BTW I'm leaving the original tests that were using weird chars because I think it's good to have tests that challenge the url encoding etc. Sure that can result in the presence of weird chars, but weird chars are a fact of life, so good to test against them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40803) Endless Loop when "provisoning config files..." when run from a build promotion
Title: Message Title Dominik Bartholdi commented on JENKINS-40803 Re: Endless Loop when "provisoning config files..." when run from a build promotion If JobPropertyImpl wold implement Item, then I think we could get this to work - whether this is the correct way to fix it - I have no idea... usually Daniel Beck has good ideas on how we could touch such thing... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40864) Cannot execute Git branch list command in order to populate dynamically a choice pipeline property component
Title: Message Title
Marcelo Filho created an issue
Jenkins / JENKINS-40864
Cannot execute Git branch list command in order to populate dynamically a choice pipeline property component
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Jan/06 4:03 PM
Priority:
Blocker
Reporter:
Marcelo Filho
At the first stage of a pipeline groovy code, is not possible to execute a git command in order to list, for example, the branches from a repository without @NonCPS or out of sandbox, for example when you're using a SCM code. Example:
String getBrancesList(String projectSSH) {
def command = "git ls-remote -h ${projectSSH}"
def proc = command.execute()
proc.waitFor()
if ( proc.exitValue() != 0 ) {
println "Error, ${proc.err.text}"
return 1;
}
def branches = proc.in.text.readLines().collect {
it.replaceAll(/[a-z0-9]*\trefs\/heads\//, '')
}
int index = branches.indexOf("master");
branches.removeAt(index);
branches.add(0, "master");
return branches.join("\n")
}
///
node('my_node') {
stage('job property') {
def branchesList = getBrancesList("m...@repo.git")
properties(
[
parameters(
choice(
choices: branchesList,
description: 'Select the branch.',
name: 'repository_branch'
)
)
]
}
}
}
Using @NonCPS pasting the pipeline code in the job configuration works but it doesn't matter if you trying retrieving via SCM.
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally and can't you make it work with new versions of jenkins? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40863) Shell task ClassNotFoundException: javax.servlet.ServletException
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-40863 Shell task ClassNotFoundException: javax.servlet.ServletException Issue Type: Bug Assignee: Kanstantsin Shautsou Components: core, remoting Created: 2017/Jan/06 3:51 PM Environment: 1.642.4 Priority: Minor Reporter: Kanstantsin Shautsou Periodically see the next stacktrace: Jan 06, 2017 12:17:30 AM org.jenkinsci.plugins.cloudstats.CloudStatistics getIdFor INFO: No support for cloud-stats-plugin by class com.github.kostyasha.yad.DockerComputer Jan 06, 2017 12:17:32 AM hudson.tasks.Shell$DescriptorImpl getShellOrDefault WARNING: null java.io.IOException: Remote call on dockers-111f8342303b failed at hudson.remoting.Channel.call(Channel.java:789) at hudson.tasks.Shell$DescriptorImpl.getShellOrDefault(Shell.java:141) at hudson.tasks.Shell.buildCommandLine(Shell.java:85) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:95) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:64) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Caused by:
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title marlene cote commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally is there a different plugin that has the same functionality? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40747) Last Build is ignored when specifying "Pin build at Perforce Label"
Title: Message Title Paul Allen commented on JENKINS-40747 Re: Last Build is ignored when specifying "Pin build at Perforce Label" Please can you confirm the P4 plugin version, there have been a few recent fixes for calculating last built change. If you recently upgraded you may need to run a Build Now to help update Jenkins records for the last build. When using the "Pin build..." option if the Jenkins Job had not been executed for a while then the next build will include all changes from the last build. The last build data is stored in the build.xml file. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40803) Endless Loop when "provisoning config files..." when run from a build promotion
Title: Message Title Michael Wiles commented on JENKINS-40803 Re: Endless Loop when "provisoning config files..." when run from a build promotion Some thoughts... My knee jerk reaction to what I'm seeing is to conclude that the folder "plugin" should not be a plugin. It has a very significant impact on the broader architecture of jenkins and to have to support both situations (without and without folder plugin) is going lead to a lot of clunky code. Folder is not part of the core model of jenkins but once a plugin has been changed to support folders it now depends on the folder plugin and you might find that so many plugins need to depend on Folder plugin... Although I guess it makes sense to migrate each plugin to support folders one at a time. Not having folders as a first class citizen does allow for some of this. What is pertinent is that the passed in JobPropertyImpl has an owner (project), which then has a parent (folder) and you can then get to the relevant config file via this folder (the way you do with the abstract folder). The issue is that each of the players, JobProperty, ItemGroup and Project all need some visibility into the existence of folders. I can't see how either promoted builds or config file provider plugins can be changed to solve this particular issue as it is not a folder that is passed in but something that exists in a folder. Ultimately both plugins need to change to somehow support folders but without folders being part of the core model I fear that change will go too deep and have too many side effects. Unless ItemGroup can somehow be made aware of its context we're not going to make much progress, and given that itemGroup is part of core I'm not sure how that is going to happen. At least the change I did stops the endless loop but it of course does not allow for config files in folders to be usable from the promoted builds plugin. As I've changed it only global config files are available for use in the promoted builds plugin. A limitation that I am happy with as I depend on promoted builds having exposure to config files. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-29222) Plugin detects the wrong build as triggered occasionally
Title: Message Title Steve Ramage commented on JENKINS-29222 Re: Plugin detects the wrong build as triggered occasionally marlene cote marlene cote I think the plugin is abandoned. The pull request was never fulfilled because the solution I used didn't work on older versions of Jenkins, and I didn't feel like patching for old versions. I can point you to the repo on GitHub if you'd like where my changes were. I think I made a few. The older versions of Jenkins are like versions from 2014 or 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-36472) Depend on Icon Shim Plugin
Title: Message Title TraceTronic GmbH closed an issue as Fixed Released in 1.15 Jenkins / JENKINS-36472 Depend on Icon Shim Plugin Change By: TraceTronic GmbH Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40441) Encoding failure: multibranch fails indexing on ATH for strange pipeline names
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40441 Re: Encoding failure: multibranch fails indexing on ATH for strange pipeline names Code changed in jenkins User: Stephen Connolly Path: src/test/java/integration/BrandingTest.java http://jenkins-ci.org/commit/branch-api-plugin/6219ef9ef106001259c18387cc7c213c4addf31d Log: Check that JENKINS-40441 is not our problem Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18862) Add an ability to specify external GIT repository for scripts
Title: Message Title Ed Mangual commented on JENKINS-18862 Re: Add an ability to specify external GIT repository for scripts I have the same requirements as the users stated above. We would like for this plugin to have the ability to point to our own repo for groovy scripts. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40862) Upstream project trigger tip revision error
Title: Message Title
Rolph Haspers created an issue
Jenkins / JENKINS-40862
Upstream project trigger tip revision error
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Jan/06 3:23 PM
Environment:
Jenkins v2.38
Labels:
pipeline tip
Priority:
Major
Reporter:
Rolph Haspers
Hi, I have a project which triggers a build in another project (pipeline / Jenkinsfile).
{
build job: "../projectName/master";
}
However, the downstream project gives errors out with the following error:
originally caused by:
Branch indexing
ERROR: Could not determine exact tip revision of master; falling back to nondeterministic checkout
Wiping out workspace first.
[Pipeline] End of Pipeline
ERROR: Could not determine exact tip revision of master
Finished: FAILURE
Can this be solved somehow?
[JIRA] (JENKINS-40608) Job Summary Of Changes disappeared in version 1.4.12
Title: Message Title Paul Allen commented on JENKINS-40608 Re: Job Summary Of Changes disappeared in version 1.4.12 Just want to clarify the problem. The expected behaviour; if you click build now (and there are no new changes) you should see no changes in the summary. If there is a new change then after a polling event or build now you should see just the built change. If your build is pinned and the change you are pinned to has been built, then subsequent builds (polling or build now) will report no change. The previous mechanism could miss calculate the 'last built change' and incorrectly trigger polling as well as reporting changes that were previously built. If you are supported Perforce customers we could raise a support ticket and meet up over a webex to take a closer look at the problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40861) Git variable for branch suffix
Title: Message Title Cameron Gocke created an issue Jenkins / JENKINS-40861 Git variable for branch suffix Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2017/Jan/06 3:03 PM Environment: Jenkins 2.19.1, Git plugin 3.0.0 Priority: Minor Reporter: Cameron Gocke I would like to have a simple variable available that represents the suffix of the branch name. In particular, we use release branches in bitbucket server for deployment. We also use releases in Jira as part of that workflow. So, if my Jira release is called app_sprint6, I create a release branch on my app repo called release/sprint6. I would like to be able to then use that name (sprint6) as a variable to tag my docker images before they are published so that there is parity across the development, release, and deployment. Currently we use $BUILD_NUMBER to tag the docker images, which in this workflow is just an arbitrary number value. The current variable for GIT_BRANCH contains the full text origin/release/sprint6 and is not usable for tagging a docker image b/c it doesn't accept the / characters.
[JIRA] (JENKINS-29736) History chart duration is wrong
Title: Message Title Iosif Gut resolved as Fixed The fix mentioned in the description was submitted via pull request: https://github.com/jenkinsci/junit-plugin/pull/61 Jenkins / JENKINS-29736 History chart duration is wrong Change By: Iosif Gut Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For
[JIRA] (JENKINS-40860) Go to the end of the expanded log
Title: Message Title Keith Zantow created an issue Jenkins / JENKINS-40860 Go to the end of the expanded log Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Jan/06 2:47 PM Priority: Major Reporter: Keith Zantow When clicking a failed stage (or directly going to it), the log does not scroll to the end, which is presumably where you could see an error. Noticed on ci: https://ci.blueocean.io/blue/organizations/jenkins/Pipeline%20Editor/detail/PR-15/1/pipeline/11 Add Comment
[JIRA] (JENKINS-29736) History chart duration is wrong
Title: Message Title Iosif Gut started work on JENKINS-29736 Change By: Iosif Gut 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-29736) History chart duration is wrong
Title: Message Title Iosif Gut assigned an issue to Iosif Gut Jenkins / JENKINS-29736 History chart duration is wrong Change By: Iosif Gut Assignee: Iosif Gut Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40850) Go to the "first" error for a pipeline execution
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-40850 Go to the "first" error for a pipeline execution Change By: Keith Zantow Summary: Go to the "first" error for a pipeline execution and end of log Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31259) Checking remote job needs delay
Title: Message Title marlene cote commented on JENKINS-31259 Re: Checking remote job needs delay can we get this fix 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-36472) Depend on Icon Shim Plugin
Title: Message Title TraceTronic GmbH resolved as Fixed Jenkins / JENKINS-36472 Depend on Icon Shim Plugin Change By: TraceTronic GmbH Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
