[JIRA] (JENKINS-36198) Toast component should define styles for wrapping and font color
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-36198 Toast component should define styles for wrapping and font color Change By: James Dumay Assignee: James Dumay Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36199) "Toaster" for managing Toast instances
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36199 "Toaster" for managing Toast instances Change By: James Dumay Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36199) "Toaster" for managing Toast instances
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-36199 "Toaster" for managing Toast instances Change By: James Dumay Assignee: James Dumay Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36175) Developer should be able to run a non-mutibranch pipeline job
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36175 Developer should be able to run a non-mutibranch pipeline job Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36169) Log does not match final style
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36169 Log does not match final style Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35719) Log should never horizontally scroll
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35719 Log should never horizontally scroll Change By: James Dumay Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36128) Duration never live reloads for running pipelines
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36128 Duration never live reloads for running pipelines Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36136) JDL Toast component React exception onActionClick
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36136 JDL Toast component React exception onActionClick Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35735) Fix Blue Ocean to run on Internet Explorer 11
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35735 Fix Blue Ocean to run on Internet Explorer 11 Change By: James Dumay Priority: Blocker Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35735) Fix Blue Ocean to run on Internet Explorer 11
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35735 Fix Blue Ocean to run on Internet Explorer 11 Change By: James Dumay Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36054) When SSE receives a disconnect the pages data should be refetched
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36054 When SSE receives a disconnect the pages data should be refetched Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35866) Handle jobs that are stored within folders
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35866 Handle jobs that are stored within folders Change By: James Dumay Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35796) Developer can stop the run of an executing pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35796 Developer can stop the run of an executing pipeline Change By: James Dumay Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36055) Summary does not update for new runs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36055 Summary does not update for new runs Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35822) Developer can view an executing pipeline
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35822 Developer can view an executing pipeline Change By: James Dumay Priority: Major Blocker In scope* the summary bar should have a round progress bar as mocked up* duration should dynamically update* Railroad component should update dynamicallyOut of scope* Log tailing UX-73* Stopping the pipeline UX-93 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35723) Tabs on result summary are not visible on non-HDPI screens
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35723 Tabs on result summary are not visible on non-HDPI screens Change By: James Dumay Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36102) Result header on Safari cuts off tabs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36102 Result header on Safari cuts off tabs Change By: James Dumay Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36100) missing version footer
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36100 missing version footer Change By: James Dumay Priority: Critical Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35788) Pagination for Summary tabs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-35788 Pagination for Summary tabs Change By: James Dumay Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35854) Add Rollbar error reporting
Title: Message Title James Dumay resolved as Fixed Jenkins / JENKINS-35854 Add Rollbar error reporting Change By: James Dumay Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35472) crash (stack trace) when open Configure System page
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-35472 crash (stack trace) when open Configure System page Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30206) Multibranch plugin: Modified properties do not propagate to existing branches
Title: Message Title
Sverre Moe edited a comment on JENKINS-30206
Re: Multibranch plugin: Modified properties do not propagate to existing branches
What is I had the status of this issue?Defined parameters are same problem accessing the defined parameter. The parameter was not accessible and an an environment parameter. I am stuck with further development of my build script without this found an example that worked for me . {code} Unless this is a different issue from my problem def param = false To define parameters within Jenkinsfile will update the branch project and make it parameterized if (getBinding() . However the next build does not pass that parameter. Accessing it with env.PARAM is always null. hasVariable("MY_PARAM")) {param = MY_PARAM}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title James Dumay commented on JENKINS-36208 Re: Queued items are not showing up Vivek Panday please also consult Cliff Meyers or Thorsten Scherler on what the most desirable API for this would be in the rest. In order to build the activity tab contents we would have to make two calls - one for listing runs and another for the queue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34294) Throttle Concurrent Builds plugin ignores builds on inheritance-projects.
Title: Message Title Jacek Tomaka commented on JENKINS-34294 Re: Throttle Concurrent Builds plugin ignores builds on inheritance-projects. So you recon this is deemed to fail: https://github.com/jenkinsci/throttle-concurrent-builds-plugin/pull/44 ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35472) crash (stack trace) when open Configure System page
Title: Message Title Mirko Günther updated an issue Jenkins / JENKINS-35472 crash (stack trace) when open Configure System page Change By: Mirko Günther Component/s: subversion-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36192) Can't save project settings due to LoadRules issue (Our case 14808)
Title: Message Title Thierry Lacour updated an issue Jenkins / JENKINS-36192 Can't save project settings due to LoadRules issue (Our case 14808) Change By: Thierry Lacour Summary: Can't save project settings due to LoadRules issue (Our case 14808) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title Vivek Pandey commented on JENKINS-36208 Re: Queued items are not showing up Chatting with James Dumay, here is plan of action: For efficiency, queued Items are cached, preferably using QueueListener, cache is managed as items in queue are added or leaving. MultiBranchPipelineImpl.getQueue() implementation looks in to the cache and returns list of queued items in latest first order Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36204) Role-Based: Users are not able to see new project on their views
Title: Message Title Oleg Nenashev resolved as Not A Defect Or he could just refresh the page manually. Closing as "Not a defect", please reopen if there is something else Jenkins / JENKINS-36204 Role-Based: Users are not able to see new project on their views Change By: Oleg Nenashev Status: Open 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-issu
[JIRA] (JENKINS-31801) Using Throttle Concurrent Builds in a Pipeline
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-31801 Using Throttle Concurrent Builds in a Pipeline Change By: Oleg Nenashev Summary: Using Throttle Concurrent Builds in a WorkFlow Pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34294) Throttle Concurrent Builds plugin ignores builds on inheritance-projects.
Title: Message Title Oleg Nenashev commented on JENKINS-34294 Re: Throttle Concurrent Builds plugin ignores builds on inheritance-projects. Inheritance project larchitecture is different from classic job types. It uses a high-level abstraction (hudson.model.Job) instead of hudson.model.AbstractProject, which is being implemented by the most of job types. Many plugins support hudson.model.AbstractProject only. So the plugin just does not support Inheritance project now. It needs some coding to add this support properly (similar to JENKINS-31801) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32142) Possibility to add Gradle settings file
Title: Message Title Dominik Bartholdi closed an issue as Duplicate Jenkins / JENKINS-32142 Possibility to add Gradle settings file Change By: Dominik Bartholdi Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32142) Possibility to add Gradle settings file
Title: Message Title Dominik Bartholdi reopened an issue Jenkins / JENKINS-32142 Possibility to add Gradle settings file Change By: Dominik Bartholdi Resolution: Duplicate Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36207) Make BluePipelne extensible
Title: Message Title Vivek Pandey resolved as Fixed Jenkins / JENKINS-36207 Make BluePipelne extensible Change By: Vivek Pandey Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30458) [Maven settings] "Replace All" does not work
Title: Message Title Steffen Breitbach commented on JENKINS-30458 Re: [Maven settings] "Replace All" does not work Well, that seems to be what I meant by saying: Either the mechanism is broken or the help text is wrong. So. This particular setting will not replace "even ones not found in the provided list of credentials" but rather remove all server credentials and then replace those stated explicitly. The help text in the corresponding help-isReplaceAll.html should be replaced, maybe to something like: Replace all servers in the Maven settings.xml file. If a server is not in the provided list of credentials, this servers credentials will be empty. Cheers Steffen Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title Vivek Pandey edited a comment on JENKINS-36208 Re: Queued items are not showing up [~jamesdumay] Its O \ (n \ ) cost in backend too. No easy way. Besides we can't serve queued items in run till Jenkins core makes projected build id as guaranteed id. For example, if a queued items is served in run, the id element is fake and if someone does GET using this id, it wont work. We can't use queueId because its not indexed and very expensive so should be avoided for frequently accessed APIs like run. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title Vivek Pandey commented on JENKINS-36208 Re: Queued items are not showing up James Dumay Its O cost in backend too. No easy way. Besides we can't serve queued items in run till Jenkins core makes projected build id as guaranteed id. For example, if a queued items is served in run, the id element is fake and if someone does GET using this id, it wont work. We can't use queueId because its not indexed and very expensive so should be avoided for frequently accessed APIs like run. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work well for blue oceans needs.The current API would work OK (not desirable to have two calls rather than one) for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - the requests 2+O\(n)!With thecurrent API rendering the Activity screen for multi-branch: * 1 call to fetch runs {{/runs}}* 1 call to fetch all branches {{/branches/}}* N calls to fetch all the queued items for all branches {{/branch/$branch/queue/}}We need to go back to the drawing board on this...It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline type so that the UI can avoid special casing and the problem described above.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work well for blue ocean oceans needs . With this The current API /runs would work OK (not desirable to have two calls rather than one) for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its the requests 2+O\(n)! With the * 1 call to fetch runs {{/runs}} * 1 call to fetch all branches {{/branches/}} * N calls to fetch all the queued items for all branches {{/branch/$branch/queue/}} We need to go back to the drawing board on this. .. It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline type so that the UI can avoid special casing and the problem described above .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its 2+O\(n)!* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline information type .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its 2+O\(n)!* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this. It would be easier if you could always expect that {{/runs}} also returned the queue - regardless of the pipeline information.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its {{ 2+O(n) }} :* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its {{ 2+O \ ( n ) }}: ! * 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay edited a comment on JENKINS-36208
Re: Queued items are not showing up
[~vivek] [~imeredith] it looks like this API could never work for blue ocean.With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue.For multi-branch this is dire - its {{2+O(n)}}:* 1 call to fetch runs* 1 call to fetch all branches* N calls to fetch all the queued items for all branchesWe need to go back to the drawing board on this.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title James Dumay commented on JENKINS-36208 Re: Queued items are not showing up Vivek Pandey Ivan Meredith it looks like this API could never work for blue ocean. With this API /runs would work OK for freestyle because the client could do a call to fetch all the runs and another call to fetch the queue. For multi-branch this is dire - its 2+O: 1 call to fetch runs 1 call to fetch all branches N calls to fetch all the queued items for all branches We need to go back to the drawing board on this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-36208
Queued items are not showing up
Change By:
James Dumay
I ran this job on blueocean.io !classic.png|thumbnail! It didn't show up as queued !blue.png|thumbnail! Calling the REST API there is nothing in the runs{code}charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/runs/ | json_pp[]{code}But there seems to be items in the queue{code}charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/queue/ | json_pp [ { "pipeline" : "freestyle", "id" : "545", "_class" : "io.jenkins.blueocean.service.embedded.rest.QueueItemImpl", "queuedTime" : "2016-06-24T04:53:33.867+", "_links" : { "self" : {"href" : "/blue/rest/organizations/jenkins/pipelines/freestyle/queue/545/","_class" : "io.jenkins.blueocean.rest.hal.Link" } }, "expectedBuildNumber" : 1 }]{ code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-36208
Queued items are not showing up
Change By:
James Dumay
I ran this job on blueocean.io !classic.png|thumbnail! It didn't show up as queued !blue.png|thumbnail! Calling the REST API there is nothing in the queue{code}charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/ runs queue / | json_pp [] {code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36208 Queued items are not showing up Change By: James Dumay Sprint: 1.0-m10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36208) Queued items are not showing up
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36208 Queued items are not showing up Issue Type: Bug Assignee: Vivek Pandey Attachments: blue.png, classic.png Components: blueocean-plugin Created: 2016/Jun/24 5:04 AM Priority: Blocker Reporter: James Dumay I ran this job on blueocean.io It didn't show up as queued Calling the REST API there is nothing in the queue charon:~ jdumay$ curl -s https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/freestyle/runs/ | json_pp [] Add Comment
[JIRA] (JENKINS-34469) robotframework pipeline-plugin compatibility
Title: Message Title
Mike Nicholson edited a comment on JENKINS-34469
Re: robotframework pipeline-plugin compatibility
+1 The pipeline plugin is critical to our workflow and good CI/CD practices in general. It would be great to see this plugin working within the build pipeline. I've attempted to add it to a Jenkinsfile as a general build step as follows: {code:groovy}step([$class: 'RobotPublisher', outputPath: '.', passThreshold: 0, unstableThreshold: 0]){code}This results in the following stack trace when that step is run:{noformat}java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:305) at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:248) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:192) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) 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(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15) at WorkflowScript.run(WorkflowScript:27) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.GeneratedMethodAccessor434.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55) at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45) at sun.reflect.GeneratedMethodAccessor439.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.gro
[JIRA] (JENKINS-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Vivek Pandey commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Michael Neale No way. Besides folder changes or any changes that has gone in has nothing to do with it. Its nothing to do with BO API, its more of how a job name is stored by jenkins that is its job.getName() is URL encoded. So the Job name is stored by jenkins as encoded, then while URL of job, generated by jenkins, the job name is url encoded as it knows the original job name is encoded of some form, so in effect the job name gets encoded twice. There is no other way to deal with it. for example if you navigate to a branch in classic UI, you will see the URL doubly encoded, e.g. https://ci.blueocean.io/job/jenkins-design-language/job/feature%252FUX-328/. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Michael Neale edited a comment on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints [~vivek] I am pretty sure this did used to work with single encoding. It would use the same URI as you would see in classic when you browsed to a multibranch pipelines branch, that is how I knew it worked. Requiring double encoding for the api seems new , as we used git flow names since the start, and we were able to see logs of feature branches . This seems to have changed since the folders rework went in, I think. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Michael Neale commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Vivek Pandey I am pretty sure this did used to work with single encoding. It would use the same URI as you would see in classic when you browsed to a multibranch pipelines branch, that is how I knew it worked. Requiring double encoding for the api seems new. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36154) Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints
Title: Message Title Michael Neale commented on JENKINS-36154 Re: Multi-branch pipelines using branches with non-standard characters result in 404's against certain REST API endpoints Yes, I suspected some clever even double encoding may be required. Jenkins uses URL encoding for branch names as they are stored as a path on disk. Git flow typically has foo/bar style naming of branches, but there are rules about what is allowed: https://wincent.com/wiki/Legal_Git_branch_names however, multibranch is not just git, and who knows what other SCM uses for their branch equivalents. Basically, think of the branch name as not really a path, but some encoded value. It is an unfortunate co-incidence that it uses URL encoding (but it kind of has to). This is also used on disk (which has occasionally causes some problems as a side effect, so that may change). Basically the branch name is what the branch name is, and is likely needed to be encoded one way or another. If it is being encoded with other paths, then it will end up double encoded, yes. I am going cross eyed just thinking about this... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34469) robotframework pipeline-plugin compatibility
Title: Message Title Mike Nicholson commented on JENKINS-34469 Re: robotframework pipeline-plugin compatibility +1 The pipeline plugin is critical to our workflow and good CI/CD practices in general. It would be great to see this plugin working within the build pipeline. I've attempted to add it to a Jenkinsfile as a general build step as follows: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml step([$class: 'RobotPublisher', outputPath: '.', passThreshold: 0, unstableThreshold: 0]) This results in the following stack trace when that step is run: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:193) at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:305) at org.jenkinsci.plugins.structs.describable.DescribableModel.buildArguments(DescribableModel.java:248) at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:192) at org.jenkinsci.plugins.workflow.steps.StepDescriptor.newInstance(StepDescriptor.java:104) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:134) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:113) at groovy.lang.GroovyObject$invokeMethod.call(Unknown Source) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:151) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:21) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:115) 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(Checker.java:123) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:15) at WorkflowScript.run(WorkflowScript:27) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:55) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:106) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:79) at sun.reflect.GeneratedMethodAccessor434.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccesso
[JIRA] (JENKINS-36207) Make BluePipelne extensible
Title: Message Title Vivek Pandey started work on JENKINS-36207 Change By: Vivek Pandey Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Mark Waite commented on JENKINS-20941 Re: Stored git credentials not used when submodule is updated That has been a relatively common problem with that wiki page. The solution I've been told to use is to add a parameter to the end of the URL. I used https://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin?foo=bar to read the correct page. The git client plugin 2.0.0-beta1 has been released to the experimental update center. It includes git submodule authentication, JGit 4.3, and requires JDK 7. It requires at least Jenkins 1.625 (the first version to mandate JDK 7). The process of preparing that release (with JGit 4.3) exposed an incompatibility which I haven't yet decided how to resolve. The incompatibility is described in a posting to the Jenkins developers mailing list. I need some more time to choose the best compromise. I really want JDK 7 because it makes the git client plugin cleaner and less susceptible to file leaks. I also want JGit 4, because JGit 4 is receiving active development, while JGit 3 is not. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36207) Make BluePipelne extensible
Title: Message Title Vivek Pandey created an issue Jenkins / JENKINS-36207 Make BluePipelne extensible Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2016/Jun/24 3:34 AM Priority: Major Reporter: Vivek Pandey At present BluePipeline implementations are hardcoded to be picked up based on inspecting Item type. What we want is for anyone to provide their implementation of BluePipeline and it gets plugged in. For example if a plugin defined their own implementation of AbstractProject and they provide their implementation of BluePipeline, their implementation of BluePipeline should be able to expose their project specific JSON response in addition whats required by BluePipeline contract. Add Comment
[JIRA] (JENKINS-36206) Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop java.lang.CharSequence int to generic-whiteliest
Title: Message Title
Owen Wood created an issue
Jenkins / JENKINS-36206
Add staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop java.lang.CharSequence int to generic-whiteliest
Issue Type:
Improvement
Assignee:
Jesse Glick
Components:
script-security-plugin
Created:
2016/Jun/24 3:28 AM
Priority:
Minor
Reporter:
Owen Wood
Pending review of course. Not sure what security implications there might be here. To reproduce:
node {
env.WORKSPACE = pwd()
test = env.WORKSPACE.drop(3)
}
Results in:
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.DefaultGroovyMethods drop java.lang.CharSequence int
at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:174)
Reproducible with Sandbox enabled (or using Jenkinsfile obviously)
[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Mark Waite commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace Adding multiple independent repository support to the existing git plugin looks extremely difficult to me. You might investigate using a Jenkinsfile in the root directory of your starting repository. I believe that Jenkinsfile can then be used to define the set of repositories you would like to checkout. There is a stackoverflow article which provides an example. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35657) Support Multibranch Workflow from 2 different github repos
Title: Message Title Bryden Oliver commented on JENKINS-35657 Re: Support Multibranch Workflow from 2 different github repos The duplicate issue covers far more and seems to involve a far more complicated solution. Although the solution proposed here could probably cover the case mentioned in the other issue, or at least a significant subset of 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-35818) Developer sees a interstitial when tab data is being displayed
Title: Message Title James Dumay stopped work on JENKINS-35818 Change By: James Dumay Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35776) Bundle all licenses in the license directory and display them on /legal
Title: Message Title James Dumay stopped work on JENKINS-35776 Change By: James Dumay Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35827) Developer sees a interstitial when pipeline result data is being loaded
Title: Message Title James Dumay stopped work on JENKINS-35827 Change By: James Dumay Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36169) Log does not match final style
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36169 Log does not match final style Change By: James Dumay Sprint: 1.0- m11 m10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36135) cannot get CHANGES BUILD_LOG BUILD_STATUS variables' value
Title: Message Title Xiangyan Li updated an issue Jenkins / JENKINS-36135 cannot get CHANGES BUILD_LOG BUILD_STATUS variables' value Change By: Xiangyan Li Component/s: email-ext-plugin Component/s: repo-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Mark Waite commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Since the git plugin doesn't read the contents of Jenkinsfile when performing polling, I'm not sure how it would honor the polling settings inside the Jenkinsfile in the repository. It seems like it would be even more challenging in a repository with more than one branch, since the polling settings might differ between branches within the same repository. I wonder if Jesse Glick has any ideas how to handle this case and JENKINS-35988 (and others like 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-36195) Pipeline polling ignores special polling rules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-36195 Pipeline polling ignores special polling rules Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36167) Don't wait for busy nodes
Title: Message Title Ella Z updated an issue Jenkins / JENKINS-36167 Don't wait for busy nodes Change By: Ella Z Triggering a job with the Node parameter (with the Node eligibility is set to All Nodes )on Node1 and Node2If Node1 is busy, Node2 won't start unless the job will start on Node1 I want Node2 to start the job, and the job for Node1 to stay in the queue until Node1 is free Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32481) git plugin does not retry when submodule update fails
Title: Message Title Scott Johnson commented on JENKINS-32481 Re: git plugin does not retry when submodule update fails This seems to still be broken in git-plugin 2.5.0 (the latest release). The pull request linked in the previous comment is still open. This bug, combined with github flakiness today, is killing all my 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-36205) is it possible to set umask 002 so files after build got that permissions ?
Title: Message Title luis ramirez assigned an issue to Oleg Nenashev Jenkins / JENKINS-36205 is it possible to set umask 002 so files after build got that permissions ? Change By: luis ramirez Assignee: luis ramirez Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36175) Developer should be able to run a non-mutibranch pipeline job
Title: Message Title James Dumay assigned an issue to Tom FENNELLY Jenkins / JENKINS-36175 Developer should be able to run a non-mutibranch pipeline job Change By: James Dumay Assignee: James Dumay Tom FENNELLY Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36175) Developer should be able to run a non-mutibranch pipeline job
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36175 Developer should be able to run a non-mutibranch pipeline job Change By: James Dumay Sprint: 1.0- m11 m10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36205) is it possible to set umask 002 so files after build got that permissions ?
Title: Message Title luis ramirez created an issue Jenkins / JENKINS-36205 is it possible to set umask 002 so files after build got that permissions ? Issue Type: Bug Assignee: luis ramirez Components: _unsorted Created: 2016/Jun/23 10:13 PM Priority: Minor Reporter: luis ramirez in every build using jenkins, group is not able to write on the files, I have been trying to set the umask to 002 with no luck. any advice please ? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1
[JIRA] (JENKINS-36204) Role-Based: Users are not able to see new project on their views
Title: Message Title eric tang commented on JENKINS-36204 Re: Role-Based: Users are not able to see new project on their views Seems the user needed to enable auto refresh on his profile. He is now able to see the new project. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36201) Build Keeper not locking the downstream Job
Title: Message Title Vairavan Sockalingam closed an issue as Fixed Silly me..Just pass the ENV variable.. Jenkins / JENKINS-36201 Build Keeper not locking the downstream Job Change By: Vairavan Sockalingam 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/opto
[JIRA] (JENKINS-35208) Unable to deploy the ear file using weblogic-deployer-plugin
Title: Message Title Raphael CHAUMIER closed an issue as Cannot Reproduce Jenkins / JENKINS-35208 Unable to deploy the ear file using weblogic-deployer-plugin Change By: Raphael CHAUMIER Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36204) Role-Based: Users are not able to see new project on their views
Title: Message Title eric tang created an issue Jenkins / JENKINS-36204 Role-Based: Users are not able to see new project on their views Issue Type: Bug Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2016/Jun/23 9:53 PM Environment: Non Prod Priority: Minor Reporter: eric tang I created a view and added an existing project. The user is able to see the project fine. However, when I created a new project and updated his view to include the project, he is not able to see the new project. I'm using role based security. As an admin, I can see the job in the view. When I give admin rights to the user, he can also see the project in his view. Has anyone seen this before? Add Comment
[JIRA] (JENKINS-14042) Add timeout on tasks
Title: Message Title Raphael CHAUMIER closed an issue as Won't Do Using adavanced configuration to set a timeout parameter Jenkins / JENKINS-14042 Add timeout on tasks Change By: Raphael CHAUMIER 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-36128) Duration never live reloads for running pipelines
Title: Message Title James Dumay commented on JENKINS-36128 Re: Duration never live reloads for running pipelines @cliffmeyers yes please - any other place you know of would be great Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36203) requestBody field is not available for Pipeline Step
Title: Message Title Isaac Cohen commented on JENKINS-36203 Re: requestBody field is not available for Pipeline Step https://github.com/jenkinsci/http-request-plugin/pull/15 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34376) Cannot easily/safely catch exceptions without disrupting job abortion
Title: Message Title Clay Gerrard commented on JENKINS-34376 Re: Cannot easily/safely catch exceptions without disrupting job abortion Can we get the JIRA component tags inline with the project name? https://wiki.jenkins-ci.org/display/JENKINS/workflow+plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33090) Ease bundles management by the administrator
Title: Message Title Arnaud Héritier commented on JENKINS-33090 Re: Ease bundles management by the administrator Jesse Glick sub-tasks aren't activated on this instance. That's why I used Epic + 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-36128) Duration never live reloads for running pipelines
Title: Message Title Cliff Meyers commented on JENKINS-36128 Re: Duration never live reloads for running pipelines James Dumay I have fixes in place for the Activity grid and the Pipeline Result header. Should I add it for the "Completed" column in the Branches and Pull Requests tab as well? And Run Detail -> Changes -> Date column? I believe those are all the places in the app. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36203) requestBody field is not available for Pipeline Step
Title: Message Title Isaac Cohen created an issue Jenkins / JENKINS-36203 requestBody field is not available for Pipeline Step Issue Type: Bug Assignee: Janario Oliveira Components: http-request-plugin Created: 2016/Jun/23 8:45 PM Priority: Major Reporter: Isaac Cohen The new requestBody field is not available as an option for the Pipeline Step. It is also not visible in the Snippet Generator. This is important for POST requests requiring the body. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-34216) Failed to reset the request input stream
Title: Message Title Joshua Spence commented on JENKINS-34216 Re: Failed to reset the request input stream Strangely, version 0.10.5 works fine for us on Jenkins 2.9. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34216) Failed to reset the request input stream
Title: Message Title Joshua Spence commented on JENKINS-34216 Re: Failed to reset the request input stream Ah sorry about that. I'm not a Java developer and I think that this was my first PR for a Java project too. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36152) Reference the upstream job by using CauseAction
Title: Message Title Oleg Nenashev commented on JENKINS-36152 Re: Reference the upstream job by using CauseAction Yep, good subject for discussion. Ideally the plugin could have a WorkspaceSelector extension point with different implementations. Unique IDs would be neat for Fingerprinting feature BTW. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36152) Reference the upstream job by using CauseAction
Title: Message Title Jesse Glick commented on JENKINS-36152 Re: Reference the upstream job by using CauseAction As noted elsewhere, I do not really recommend relying on UpstreamCause, which was mainly intended as informational (for human display), not an authoritative source. Better IMO for the upstream build to name a particular workspace somehow, and pass this information as a parameter to the downstream build. Explicit, debuggable, safe for concurrent use. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32631) ability to configure throttling of matrix parents and children
Title: Message Title Daniel Spilker resolved as Fixed Will be fixed in 1.48. Jenkins / JENKINS-32631 ability to configure throttling of matrix parents and children Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36202) Listing tfs workspaces fails with 4.1.0
Title: Message Title Oleg N commented on JENKINS-36202 Re: Listing tfs workspaces fails with 4.1.0 Is there a way to see the exact command being called in the console log in the new 4.1.0 plugin, like it was possible in the 3.2 plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33685) filter stacktrace in all cases
Title: Message Title Ivan Fernandez Calvo closed an issue as Won't Do Jenkins / JENKINS-33685 filter stacktrace in all cases Change By: Ivan Fernandez Calvo Status: In Progress 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-33090) Ease bundles management by the administrator
Title: Message Title Jesse Glick commented on JENKINS-33090 Re: Ease bundles management by the administrator A Story plus Tasks would be more appropriate for this sort of 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-33090) Ease bundles management by the administrator
Title: Message Title Jesse Glick started work on JENKINS-33090 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-33090) Ease bundles management by the administrator
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-33090 Ease bundles management by the administrator Change By: Arnaud Héritier Summary: Ease the management bundles management by the administrator Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26989) Inject env variables via stored script
Title: Message Title
Alexander Komarov edited a comment on JENKINS-26989
Re: Inject env variables via stored script
Agreed that it would be nice. In the meantime, I've worked around this by retrieving scripts via http from jenkins userContent, one (Scripts in that directory get auto - updated from scm via puppet).All scripts return a closure.One- liner for brevity: {code:java}evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)(){code}Script example:{code:java}return { ['something': 'someValue']}{code} (Scripts in that directory get auto-updated from scm via puppet). Scripts return a closure. Same with parameter passed to the shared script:{code:java}evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)('some-parameter-value'){code}Script example:{code:java}return { myParam -> [ 'something': myParam]}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32479) multiple git repositories sometimes fail to checkout some of them into subdirectory
Title: Message Title Terry Ewing commented on JENKINS-32479 Re: multiple git repositories sometimes fail to checkout some of them into subdirectory I think this issue is the same as https://issues.jenkins-ci.org/browse/JENKINS-27668. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26989) Inject env variables via stored script
Title: Message Title
Alexander Komarov commented on JENKINS-26989
Re: Inject env variables via stored script
Agreed that it would be nice. In the meantime, I've worked around this by retrieving scripts via http from jenkins userContent, one-liner for brevity:
evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)()
Script example:
return {
['something': 'someValue']
}
(Scripts in that directory get auto-updated from scm via puppet). Scripts return a closure. Same with parameter passed to the shared script:
evaluate("${jenkins.model.Jenkins.getInstance().getRootUrl()}/userContent/my-script-name.groovy".toURL().text)('some-parameter-value')
Script example:
return { myParam ->
[ 'something': myParam]
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34517) Pipeline is unable to locate global libraries when build attempts to continue on restart
Title: Message Title
davidkarlsen edited a comment on JENKINS-34517
Re: Pipeline is unable to locate global libraries when build attempts to continue on restart
Even worse - the whole job can go into an illegal state. The job broke on startup with this issue 1), but the next is waiting for the previous one to complete1){noformat}18:57:11 Waiting for builds [717]Resuming build[Pipeline] End of Pipeline[Bitbucket] Notifying commit build result[Bitbucket] Build result notifiedjava.io.IOException: Failed to load pe{noformat}2){noformat}19:31:54 Waiting for builds [718]{noformat} so now we're totally stuck Update: I see this registered as https://issues.jenkins-ci.org/browse/JENKINS-28183
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27668) Add support for multiple git repositories in a single workspace
Title: Message Title Terry Ewing commented on JENKINS-27668 Re: Add support for multiple git repositories in a single workspace Found this thread after experiencing the same issue. My job is configured with two git repos. When the job runs it appears to check out both repos but the workspace only shows contents from the first. I believe this is a bug because the configuration in the UI isn't being produced in the workspace. I'm sure I can work around the issue and am hoping maintainers can find a solution soon. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29390) Parameterization for Docker Container configuration.
Title: Message Title Antonio Beyah commented on JENKINS-29390 Re: Parameterization for Docker Container configuration. Can we also make a similar consideration for volumes? I would like the volumes mounted for workspace and target paths to be configurable. The current (default) is great for most cases but there are areas where it falls apart, namely places where the same directories are used by the job running inside the container and are also mounted. For example, JENKINS_HOME is mounted inside the container, but I have an RPM that is building/installing a RPM that is creating those directories (the jenkins rpm), so in this case I would like the JENKINS_HOME to not match the paths in the rpm. In a sense, in some instances I want the file system to be completely isolated from the host machine. I'm thinking it would be nice if under 'volumes' the default was to have the ones that are currently hardcoded, but to allow the volumes to be completely configurable. I'm curious to your thoughts on that, if you are open to it I may be able to throw a PR together that adds that support. If you want I can open a separate issue to discuss configurable volumes, just let me know. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
