[JIRA] (JENKINS-54152) restart jenkins when not runned as service
Title: Message Title Ronny Borchert commented on JENKINS-54152 Re: restart jenkins when not runned as service I tried the "interactive" and it seems to work. The PC has disabled UAC, just for future info. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54153) Creating workspace without sync?
Title: Message Title Kevin Park created an issue Jenkins / JENKINS-54153 Creating workspace without sync? Issue Type: New Feature Assignee: Unassigned Components: p4-plugin Created: 2018-10-19 05:36 Priority: Minor Reporter: Kevin Park This is related to Swarm automated test feature; Here is a scenario, 1. An user requests a swarm review, Jenkins job will be run. 2. Job will create workspace using template workspace, template workspace's view mapping has all depots. 3. Any files in the depots can be requested, and then unshelved from a review, and run some tests. However, since there are so many files in depot, p4 sync -n and p4 sync -k commands are very slow. Hence, the customer would like to know if there is a way to create workspace only without any sync command. Add Comment
[JIRA] (JENKINS-54152) restart jenkins when not runned as service
Title: Message Title Oleg Nenashev edited a comment on JENKINS-54152 Re: restart jenkins when not runned as service Hello,> We have GUI tests running which are needed a logged in user and that the jenkins instance is running under this logged in instance. Because no service is running the checkbox "Restart Jenkins when installation is complete and no jobs are running" is not available. So please remove this useless text or provide an alternative tex It may be a separate UX issue> Is it possible to integrate an alternative way to restart jenkins? Maybe you want to start from setting an "interactive" flag in the Windows service settings: [https://github.com/kohsuke/winsw/blob/master/doc/xmlConfigFile.md#interactive] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54152) restart jenkins when not runned as service
Title: Message Title Oleg Nenashev commented on JENKINS-54152 Re: restart jenkins when not runned as service Hello, > We have GUI tests running which are needed a logged in user and that the jenkins instance is running under this logged in instance. Because no service is running the checkbox "Restart Jenkins when installation is complete and no jobs are running" is not available. So please remove this useless text or provide an alternative tex Maybe you want to start from setting an "interactive" flag in the Windows service settings: https://github.com/kohsuke/winsw/blob/master/doc/xmlConfigFile.md#interactive Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54152) restart jenkins when not runned as service
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-54152 restart jenkins when not runned as service Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-10-19 05:00 Environment: Windows Server 2012 Labels: restart service Priority: Minor Reporter: Ronny Borchert We have GUI tests running which are needed a logged in user and that the jenkins instance is running under this logged in instance. Because no service is running the checkbox "Restart Jenkins when installation is complete and no jobs are running" is not available. So please remove this useless text or provide an alternative text. Is it possible to integrate an alternative way to restart jenkins? i.e. provide a path to a batch file which will be executed to start jenkins again, when checkbox "Restart Jenkins when installation is complete and no jobs are running" is checked or assign a job which do this, question is here how shutdown can be done or would it work when a child node runs as the logged in user and jenkins it self is running as a service?
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline I have not yet tried it, but studying the pipeline-maven code it looks like that should be easy to fix as well, by pregenerating notes. The ansicolor case is harder because pregenerating notes looks complex. SimpleHtmlNote would be the most convenient possible vector for a stored-XSS attack were it not for SECURITY-382. There is a range of element names apparently passed to AnsiAttributeElement, which would not be a major problem, but for some types there is also a range of colors passed in, and for FGBG there is a pair of colors, thus 8 × 8 = 64 possibilities that would need to be pregenerated. Again creating a ConsoleAnnotatorFactory would be by far the preferable solution in general, even if there were no ConsoleNote compatibility issue—you pay the cost of scanning only during HTML rendering in the classic UI, if even ever shown; the log file is not bloated by large encrypted notes; and you are not in a Catch-22 w.r.t. Blue Ocean—but the extensive logic in AnsiHtmlOutputStream + AnsiOutputStream would have to be reworked significantly to follow this API, which is not structured as a filter on a stream but as a hook able to insert markup. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Jie Shen commented on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin Hi Badal Kotecha, Yes, there are some problems here. And I have created an issue on Github to entirely fix this. For now, there is a temporarily solution for you to work around here. In the Azure Active Directory Matrix-based security section, you need to have two users in the matrix to make it work for accessing Jenkins API. The auto-completion will provide you a user name like 'username (object id)'. Besides this, you need to add a user name like 'username (user ID)' and give it the reading permission. By that, the API things should work. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54151) Update CWP to JCasC 1.0
Title: Message Title Oleg Nenashev started work on JENKINS-54151 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54151) Update CWP to JCasC 1.0
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54151 Update CWP to JCasC 1.0 Issue Type: Improvement Assignee: Oleg Nenashev Components: custom-war-packager Created: 2018-10-19 00:52 Labels: jcasc-compatibility Priority: Minor Reporter: Oleg Nenashev There were some changes in config file resolution after the release of JCasC 1.0. CWP needs to be updated to support the released versions of JCasC Add Comment
[JIRA] (JENKINS-54150) Add config option to ignore certificate errors
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-54150 Add config option to ignore certificate errors Issue Type: Improvement Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-10-19 00:28 Priority: Minor Reporter: Owen Mehegan This plugin currently has no configuration option to allow it to ignore errors with the certificate being used on Bitbucket. This means that if someone has a self-signed cert, they have to import it into the JVM trust store used by Jenkins before branch indexing will work. Doing this is a bit of a hassle. Most other integrations of this sort have a check box option to allow the user to disable certificate validation. Add Comment
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Robert Middleton commented on JENKINS-54120 Re: Output directory or source file null. Okay, first thing: make sure that you have your checkout in a sub-folder(e.g. source/). Because of how dpkg works, it will generate the files needed for the build in the parent directory, so that's probably why it's failing. Next, you also will need to clean your workspace before the new build; I generally nuke the entire workspace, but it should be possible to just delete *.tar.gz and *.dsc if the checkout would take too long. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Dana Goyette commented on JENKINS-37324 Re: We would like a more meaningful description of a step Thanks for the hint about the issue being variables. That seems to be it: if I use any variables (in the stock sh step's command or the labelledShell step's label), then the label is just silently ignored! Should I file a separate ticket for that brokenness? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46674) Direct SQS integration causes JSONException
Title: Message Title Kartik Ramachandran edited a comment on JENKINS-46674 Re: Direct SQS integration causes JSONException is there any update on this? We are hitting the same issue. There seems to be a PR for this issue. Can someone please review and merge? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem
Title: Message Title Cyrille Le Clerc commented on JENKINS-54139 Re: Jacoco report rendering problem As a workaround, can you disable the automated publishing of the jacoco report publisher of the pipeline maven plugin: Navigate to "Manage Jenkins / Global Tools Configuration" In the "Pipeline Maven configuration" section, click on "Add Publisher Options" and select "Jacoco Publisher" Check the "Disabled" checkbox Save the configuration I'll look at the bug asap Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-54139 Jacoco report rendering problem Change By: Cyrille Le Clerc Attachment: JENKINS-54139.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34377) job-restrictions Job Property does not support Pipeline Plugin
Title: Message Title Oleg Nenashev commented on JENKINS-34377 Re: job-restrictions Job Property does not support Pipeline Plugin No update. The described use-case can be rather done by Authorize Project and user roles in matrix-auth/role-strategy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34377) job-restrictions Job Property does not support Pipeline Plugin
Title: Message Title Michael DeGuzis commented on JENKINS-34377 Re: job-restrictions Job Property does not support Pipeline Plugin The last update was a year ago, any update? This is one key thing that is holding us back from pinning nodes to certain users so we don't have to use a power user to connect to the nodes and then restrict who can use the node. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler edited a comment on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox As final explanation why FF stopped working is that since we did not provide a callback to the onClick, FF correctly stop stops propagating and all other browser are wrong to propagate the event to a submit.We fixed the f:submit however the problem may occur in other parts but the solution will always be to provide a default fallback for onClick. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler edited a comment on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox As final explanation why FF stopped working is that since we did not provide a callback to the onClick, FF is correctly stop propagating and all other browser are wrong to propagate the event to a submit.We fixed the f:submit however the problem may occur in other parts but the solution will always be to provide a default fallback for onClick. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox As final explanation why FF stopped working is that since we did not provide a callback to the onClick, FF is correctly stop propagating and all other browser are wrong to propagate the event to a submit. We fixed the f:submit however the problem may occur in other parts but the solution will always be to provide a default fallback for onClick. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Markus Maga commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification Jesse Glick perhaps, suggestions welcome But having milestones that can be bound to one or more parameters makes sense to me. But I don't see a reason not to offer this flexibility, it would give more super powers to parameterised builds Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox to your last question I guess Daniel Beck or R. Tyler Croy can make this happening. The patch just needs some approves and it is done. BTW I just verified that other parts of jenkins will work as expected and I left a comment in the FF bugzilla to link to the pr as fix when people run into the issue on older versions of jenkins. HTH and thanks for all your hard work at mozilla!!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler edited a comment on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox to your last question I guess [~danielbeck] or [~rtyler] can make this happening happen . ;)The patch just needs some approves and it is done. BTW I just verified that other parts of jenkins will work as expected and I left a comment in the FF bugzilla to link to the pr as fix when people run into the issue on older versions of jenkins.HTH and thanks for all your hard work at mozilla!!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Wonderful. In that case I assume you want to finish up the patch now? Is there something else you would need help with? My remaining question would be if we could also get this into a LTS release once it landed on master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title
Prem Gangana commented on JENKINS-50975
Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Hi Paul Allen, I have tested this with the build 281. It is using "jenkins-lib-${NODE_NAME}-${JOB_NAME}" + id as client name now, but i would suggest replacing / with _ in id instead of . (dot). So this is unique across different jobs due to JOB_NAME in there. However, the issue will surface if a given job has two builds triggered at / almost at the same time, since the jenkins appends @ to the build workspace, and so the client root dirs will be different. I would suggest adding WORKSPACE base name some where in there.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Jesse Glick commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification prevent running simultaneous deployments for the same app to the same environment This sort of logic should probably be moved out of Jenkins itself into a deployment tool. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50892) Pipeline jobs stuck after restart
Title: Message Title
Jesse Glick edited a comment on JENKINS-50892
Re: Pipeline jobs stuck after restart
No, the {{durable-task}} plugin. For most Pipeline issues, the version of Jenkins core is irrelevant. I presume [~svanoort] meant something else, since there is no such version of this plugin.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50892) Pipeline jobs stuck after restart
Title: Message Title Jesse Glick commented on JENKINS-50892 Re: Pipeline jobs stuck after restart No, the durable-task plugin. For most Pipeline issues, the version of Jenkins core is irrelevant. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Markus Maga commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification I've also been looking for something similar. Our use case is that we have a shared job for deployment, we have multiple multibranch jobs which all trigger a parameterised pipeline job. In this pipeline job I'd like to combine milestones & locks to prevent running simultaneous deployments for the same app to the same environment. I can use locks to only deploy one of each app at a time (different apps can deploy in parallel). But it would be nice to use the milestone with the suggested ordinalGroup in combination with locks using inversePrecedence: true. Do you have an alternative solution to this Antonio Muñiz? I see no need to have to create new jobs for each possible application & environment combination. Did you find any solution Tobias Peitzsch? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline Fix for the ant plugin was easy at least. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50892) Pipeline jobs stuck after restart
Title: Message Title Marley Kudiabor commented on JENKINS-50892 Re: Pipeline jobs stuck after restart Sam Van Oort Durable task is currently on 1.26 does 2.23 imply the jenkins version itself? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34311) execute scripts on axes after all build steps are finished
Title: Message Title Wojciech Półtorak commented on JENKINS-34311 Re: execute scripts on axes after all build steps are finished attached also config file for my workaround with 'Send files and execute commands over SSH' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34311) execute scripts on axes after all build steps are finished
Title: Message Title Wojciech Półtorak updated an issue Jenkins / JENKINS-34311 execute scripts on axes after all build steps are finished Change By: Wojciech Półtorak Attachment: config workaround.xml Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Mark Waite commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ Andrew LoPinto I think the best way you could help would be to debug on a macOS machine to see why command line git launched from the Jenkins git client plugin can't find the git LFS binary. I don't have a macOS machine. It works on FreeBSD as I expected. FreeBSD is the closest approximation I have to macOS. For example, you might investigate (with Java debugger or otherwise): PATH setting of command line git when run on macOS Homebrew special cases (if any) for git on macOS Workarounds like installing command line git outside homebrew (in case that allows git-lfs to be found) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted @Carlos Sanchez will try tomorrow . Appreciate your commits Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted @Carlos Sanchez will try tomorrow Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Andrew LoPinto commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ I have the same issue as Serghei, OSX, and git-lfs is installed at --system. Similarly, I cannot move the git-lfs binary to /usr/bin because of Apple System Integrity. Hoping for some help on this one, we do a lot of xCode builds that we want to move to an OSX Slave. Anything I can provide to help here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53952) Linux slaves are not starting anymore
Title: Message Title Matt Hoy commented on JENKINS-53952 Re: Linux slaves are not starting anymore Seeing identical issue using M5.Xlarge, latest Jenkins, and Spot Instances. If I hit "Launch Agent" before the timeout is hit, but after it's completed booting it is successfully able to add it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline Have a functional test demonstrating the essential aspect of the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick started work on JENKINS-54133 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44325) Failed to serialize jenkins.model.Jenkins#securityRealm for class hudson.model.Hudson
Title: Message Title
Florian Forster commented on JENKINS-44325
Re: Failed to serialize jenkins.model.Jenkins#securityRealm for class hudson.model.Hudson
I ran into this issue today after upgrading Jenkins and all plugins. I managed to resolve the issue and get Jenkins to start again by adding {{ read:org,user:email,repo}} to the block in /var/lib/jenkins/config.xml. HTH, —octo
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Thorsten Scherler commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox https://youtu.be/oT7orP-FdMs I just tested on master Henrik Skupin and it shows the issue description. I am pretty confident that the PR fixes the issue (not by winning a beauty competition, but...) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54133 No ANSI coloring on slave agents in pipeline I am afraid there are several more cases where a plugin offers a ConsoleLogFilter (whether directly via BodyInvoker.mergeConsoleLogFilters, or indirectly via CoreWrapperStep calling SimpleBuildWrapper.createLoggerDecorator) that is Serializable on the master (so, can be tracked in program.dat) yet is not safely remotable, typically because it creates a ConsoleNote which is not (or reasonably could not be) pregenerated on the master side and transmitted to the agent in encoded form. This is one example in the ant plugin; the pipeline-maven plugin similarly does colorizing; the logstash plugin has a call which would not work remotely, though I am not much concerned since this use case is addressed directly by JEP-210; pipeline-utility-steps has a tee step but this does work. So I need to think about whether there is a general way to either detect filters which would add a ConsoleNote and process them master-side when using the default log storage; or securely pregenerate the note; or rework all of these to support remote filtering. Change By: Jesse Glick Component/s: workflow-api-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-34311) execute scripts on axes after all build steps are finished
Title: Message Title Wojciech Półtorak commented on JENKINS-34311 Re: execute scripts on axes after all build steps are finished Hi Daniel, at the time of creating this ticket I've been struggling with running post action after all build steps on all nodes in cluster (aka slaves in matrix project) were finished. So I created a workaround to run post build script on the whole matrix and use 'Send files and execute commands oveer ssh' plugin to start servers remotely. Instead I would expect to run simple shell command post action on axes but only when all steps on all slaves are finished (only if build pohase is finished on all nodes). Please have a look at the diagrams. The top one was what I experienced, where one of my applications was being started too early, when db was not ready at the time; the bottom one would be ideal solution in which Post build phase would be executed only if all build phases from slaves were finished. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34311) execute scripts on axes after all build steps are finished
Title: Message Title Wojciech Półtorak updated an issue Jenkins / JENKINS-34311 execute scripts on axes after all build steps are finished Change By: Wojciech Półtorak Attachment: post build steps on axes - wait for all build steps to finish.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54149) Ability to add HTML text on login page
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-54149 Ability to add HTML text on login page Change By: Rick Liu Currently, when Global Security Access Control is enable,the login page displays only "User" and "Password" textbox textfield form.It'd be great if "Configure System" or "Configure Global Security"could provide a section for Admin user to add HTML-style text,which would show up on the login page before user login. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54149) Ability to add HTML text on login page
Title: Message Title Rick Liu created an issue Jenkins / JENKINS-54149 Ability to add HTML text on login page Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-10-18 18:38 Environment: Jenkins 2.121.3 Priority: Major Reporter: Rick Liu Currently, when Global Security Access Control is enable, the login page displays only "User" and "Password" textbox form. It'd be great if "Configure System" or "Configure Global Security" could provide a section for Admin user to add HTML-style text, which would show up on the login page before user login. Add Comment
[JIRA] (JENKINS-46674) Direct SQS integration causes JSONException
Title: Message Title Kartik Ramachandran commented on JENKINS-46674 Re: Direct SQS integration causes JSONException is there any update on this? We are hitting the same issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title
Jesse Glick edited a comment on JENKINS-54133
Re: No ANSI coloring on slave agents in pipeline
Likely similar cause to JENKINS-54081—console notes generated in the agent JVM are not trusted and thus ignored during rendering. The best fix would likely be analogous to what I did for JENKINS-48344: deprecate the build wrapper at least for Pipeline, and replace the contextual {{ConsoleLogFilter}} with a global {{ TaskListenerDecorator ConsoleAnnotatorFactory }} that is able to render ANSI escape sequences in the HTML view rather than embedding {{SimpleHtmlNote}} objects. This would have the same efficiency benefit as for JENKINS-48344 (get rid of a vast volume of junk in {{log}}), as well as improving Blue Ocean compatibility with a major sore point with this plugin today: you can choose to either enable the wrapper and thus render colors in classic UI but see plain text in BO; or do nothing and thus render colors in BO but see raw escape sequences in classic UI.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Matthew Kelly commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I also have the same issue, and raised it here as well: JENKINS-54144 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17200) SCM.TAG permission not eagerly loaded
Title: Message Title Matt Sicker commented on JENKINS-17200 Re: SCM.TAG permission not eagerly loaded What if we had a sort of PermissionProvider meta-inf service which, when invoked, returns a collection of permissions to register. Due to initialization ordering, this might not be the best class to use a whiteboard pattern on (which is essentially what the existing extension-based permission model is doing). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Can you try building the JENKINS-53297 branch in PR-385 and see what is the error now? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Simply rerunning appeared _to work – i.e., the build succeeded – but it didn't actually "save issues for the next build" (despite the log message to that effect), so didn't actually attempt to parse the changelog again, which avoided the error. If I made a new commit with a JIRA ID in it, _then reran the build, it failed again. 3.0.2 has been stable so far since reverting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Nick Jones edited a comment on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 Simply rerunning _appeared _to _appeared_ to work -- i.e., the build succeeded -- but it didn't actually "save issues for the next build" (despite the log message to that effect), so didn't actually attempt to parse the changelog again, which avoided the error. If I made a new commit with a JIRA ID in it, _then_ reran the build, it failed again. 3.0.2 has been stable so far since reverting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Nick Jones updated an issue Jenkins / JENKINS-54128 Timestamper causes lots of WARNING messages in the log (getLogFile call) Change By: Nick Jones Component/s: workflow-job-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54128) Timestamper causes lots of WARNING messages in the log (getLogFile call)
Title: Message Title Nick Jones commented on JENKINS-54128 Re: Timestamper causes lots of WARNING messages in the log (getLogFile call) I'm getting this – or something very similar to it – myself, running a pre-release build of Timestamper 1.18.11 (from JENKINS-54081): Avoid calling getLogFile on #31 java.lang.UnsupportedOperationException at org.jenkinsci.plugins.workflow.job.WorkflowRun.getLogFile(WorkflowRun.java:1064) at hudson.plugins.warnings.WarningsPublisher.parseConsoleLog(WarningsPublisher.java:371) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:312) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:69) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:298) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) I don't think it's actually Timestamper, but rather the changes in Pipeline Job 2.26. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52889) new lines in secret is substituted by spaces when reading via Vault plugin
Title: Message Title fragpit fragpit commented on JENKINS-52889 Re: new lines in secret is substituted by spaces when reading via Vault plugin Same for me, looks like it's unable to work with certificates stored as secrets using this plugin without additional formatting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53394) A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance
Title: Message Title Jesse Glick assigned an issue to Ramon Leon Jenkins / JENKINS-53394 A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance Change By: Jesse Glick Assignee: Javier Raez Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53394) A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance
Title: Message Title Jesse Glick updated JENKINS-53394 Jenkins / JENKINS-53394 A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53394) A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance
Title: Message Title Jesse Glick started work on JENKINS-53394 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54143) Cannot create new users in 2.138.2
Title: Message Title Daniel Beck edited a comment on JENKINS-54143 Re: Cannot create new users in 2.138.2 bq. It should be fairly easy to reproduceI cannot. Both customizing the 'admin' user in the setup, and creating new users in the built-in security realm afterwards works for me on 2.138.2. While I used the docker image for convenience, I cannot imagine what could be different with the RPM to cause this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54143) Cannot create new users in 2.138.2
Title: Message Title Daniel Beck commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 It should be fairly easy to reproduce I cannot. Both customizing the 'admin' user in the setup, and creating new users in the built-in security realm afterwards works for me on 2.138.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54148) Failure in case node name contains space: Illegal char <">
Title: Message Title Chris J created an issue Jenkins / JENKINS-54148 Failure in case node name contains space: Illegal char <"> Issue Type: Bug Assignee: Unassigned Components: elastic-axis-plugin Created: 2018-10-18 16:17 Environment: Jenkins 2.138.2 elastic-axis: 1.2 Priority: Critical Reporter: Chris J When a label matches nodes having space in their names, the job build fails with: java.nio.file.InvalidPathException: Illegal char <"> at index 83: C:\jenkins_slave\workspace\MyJobName\label\"My machine" Please add support for spaces in node names. Thank you Add Comment
[JIRA] (JENKINS-54147) SSH protocol not supported
Title: Message Title Andy Airey created an issue Jenkins / JENKINS-54147 SSH protocol not supported Issue Type: Bug Assignee: James Strachan Components: bitbucket-branch-source-plugin, jx-pipelines-plugin Created: 2018-10-18 16:12 Environment: New Jenkins X setup Priority: Major Reporter: Andy Airey On a new Jenkins X install after doing a `jx import`, we can see the multibranc scan log give the following errors: Nothing is detected and the build(s) does not start. [Thu Oct 18 16:07:27 UTC 2018] Starting branch indexing... ERROR: [Thu Oct 18 16:07:27 UTC 2018] Could not update folder level actions from source f82b5bae-d2eb-11e8-891f-28f10e15fb27 org.apache.http.HttpException: ssh protocol is not supported at org.apache.http.impl.conn.DefaultRoutePlanner.determineRoute(DefaultRoutePlanner.java:89) at org.apache.http.impl.client.InternalHttpClient.determineRoute(InternalHttpClient.java:125) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) Caused: org.apache.http.client.ClientProtocolException at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:187) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:655) Caused: java.io.IOException: Communication error for url: /rest/api/1.0/projects/dms/repos/dms at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:685) at
[JIRA] (JENKINS-53783) When providing comma or newline separated values in .mar file entry, the particular entries seems to not be trimmed
Title: Message Title Petr Vlasek closed an issue as Fixed Fixed in 1.0.2 Jenkins / JENKINS-53783 When providing comma or newline separated values in .mar file entry, the particular entries seems to not be trimmed Change By: Petr Vlasek Status: Open Closed Resolution: Fixed Released As: https://github.com/jenkinsci/ca-service-virtualization-plugin/blob/master/CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53782) Incorrect test name in CA Service Virtualization report
Title: Message Title Petr Vlasek closed an issue as Fixed Fixed in 1.0.2 Jenkins / JENKINS-53782 Incorrect test name in CA Service Virtualization report Change By: Petr Vlasek Status: Open Closed Resolution: Fixed Released As: https://github.com/jenkinsci/ca-service-virtualization-plugin/blob/master/CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53784) Unable to deploy test in master-slave configuration
Title: Message Title Petr Vlasek closed an issue as Fixed Fixed in 1.0.2 Jenkins / JENKINS-53784 Unable to deploy test in master-slave configuration Change By: Petr Vlasek Status: Open Closed Resolution: Fixed Released As: https://github.com/jenkinsci/ca-service-virtualization-plugin/blob/master/CHANGELOG.md Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title
Paul Allen edited a comment on JENKINS-50975
Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root
I have recently made changes to Global Library workspaces for multiple instances JENKINS-53922 [ https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/281/ ] I may need to add {{$ \ {EXECUTOR_NUMBER}}} to the Global Library Workspace name formatter:In file GlobalLibraryScmScurce.java:43{code:java}setFormat("jenkins-lib-${NODE_NAME}-${JOB_NAME}" + id);{code} {code:java}setFormat("jenkins-lib-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}" + id);{code} Did you want to try this out and build it yourself or I can submit a change for you to try on the nightly build? (Just re-reading your comment and logs - Build 281 might be enough without the EXECUTOR_NUMBER)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54131) "Failed to parse changelog" in JIRA plugin 3.0.3
Title: Message Title Brian DeBlis commented on JENKINS-54131 Re: "Failed to parse changelog" in JIRA plugin 3.0.3 I get the same error, but if I re-run a second time, it works. It is just that first run for a triggered build that makes it fail. I am also reverting back to 3.0.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50975) Concurrent Groovy Shared Library syncs on different jobs use same workspace root
Title: Message Title
Paul Allen commented on JENKINS-50975
Re: Concurrent Groovy Shared Library syncs on different jobs use same workspace root
I have recently made changes to Global Library workspaces for multiple instances JENKINS-53922 https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/281/ I may need to add ${EXECUTOR_NUMBER} to the Global Library Workspace name formatter: In file GlobalLibraryScmScurce.java:43
setFormat("jenkins-lib-${NODE_NAME}-${JOB_NAME}" + id);
setFormat("jenkins-lib-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}" + id);
Did you want to try this out and build it yourself or I can submit a change for you to try on the nightly build?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54143) Cannot create new users in 2.138.2
Title: Message Title Foo Bar commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 I don't have any logs, I ended up installing an older version to get the whole thing going. It should be fairly easy to reproduce though since I tried apt-get purge jenkins followed by apt-get install jenkins the first time I bumped into this, and the same issue happened. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52857) Cannot find git-lfs when it is not installed in /usr/bin/
Title: Message Title Thomas Roberts commented on JENKINS-52857 Re: Cannot find git-lfs when it is not installed in /usr/bin/ I am having the same issue on OSX, with my git and git lfs installed through brew. This has happened on two iMacs for me (one fresh install, one existing/in use) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
Title: Message Title Paul Allen started work on JENKINS-53723 Change By: Paul Allen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
Title: Message Title
Paul Allen commented on JENKINS-53723
Re: [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
I you wanted to parameterise the pin field with ${Changelist} could you set a default value of @now for situations when it is not defined? Although this may pickup newer values during polling and possibly trigger unwanted builds.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54146) Job History Plugin 2.18.2 - XML view not working
Title: Message Title farukh khan created an issue Jenkins / JENKINS-54146 Job History Plugin 2.18.2 - XML view not working Issue Type: Bug Assignee: Stefan Brausch Attachments: Jenkins-Error.JPG Components: jobconfighistory-plugin Created: 2018-10-18 15:39 Environment: Development Labels: plugin Priority: Critical Reporter: farukh khan XML view option for Job Config History stopped working after upgrading the Jenkins LTS 2.121.1 to 2.138.1. Job Configuration History Plugin 1.18 to 1.18.2. Viewing as RAW works, however XML throws an error This page contains the following errors: error on line 1 at column 1: Document is empty Below is a rendering of the page up to the first error.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
So i can only say that the issue in this ticket was now reproduced by me:(IKS 1.11, Plugin 1.12.4 or 1.12.9, happens on both){code:java}[testingSimple] Running shell script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of Pipelinejava.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.waitUntilExists(BaseOperation.java:959) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:219) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:37) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:417) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:255) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:236) at hudson.Launcher$ProcStarter.start(Launcher.java:454) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:185) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:98) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:264) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:270) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor142.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)Caused: java.io.IOException: Failed to execute shell script inside container [java] of pod [localhost]. Timed out waiting for container to become ready! at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:438) at
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted [~dcurrie] IBM container registry "cr build" command uses local docker deamon. I just tried it and it build locally.So i think there are only 2 workarounds:1. Having docker build Slave on some VM outside of K82. Using some Java based building service like kaniko See also [https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
So i can only say that the issue in this ticket was now reproduced by me:(IKS 1.11, Plugin 1.12.4 or 1.12.9, happens on both){code:java} [ testingSimple] Running shell script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of Pipelinejava.lang.InterruptedException: sleep interrupted at java.lang.Thread.sleep(Native Method) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.waitUntilExists(BaseOperation.java:959) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:219) at io.fabric8.kubernetes.client.dsl.base.HasMetadataOperation.waitUntilReady(HasMetadataOperation.java:37) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:417) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:255) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:236) at hudson.Launcher$ProcStarter.start(Launcher.java:454) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:185) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:98) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:264) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:270) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:178) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor142.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) 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:157) at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)Caused: java.io.IOException: Failed to execute shell script inside container [java] of pod [localhost]. Timed out waiting for container to become ready! at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.waitUntilContainerIsReady(ContainerExecDecorator.java:438) at
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[ https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199 ] I will evaluate now if IKS 1.11 supports all other operations :Update Edit:{color:#00}[https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118]{color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[https://stackoverflow.com/questions/52179148/jenkins-kubernetes-plugin-with-containerd/52871199#52871199]I will evaluate now if IKS 1.11 supports all other operations:Update Edit:{color:#00}[https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118]{color} {color:#00}Seems like even if you find a workaround for docker in docker, now the problem is that with this plugin no sh can be executed inside new containers{color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori updated an issue
Jenkins / JENKINS-53297
Kubernetes v1.11 - ChannelClosed after job delaying aborted
Change By:
leon gregori
Comment:
{color:#00}[https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118]{color}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted https://wiki.jenkins.io/display/JENKINS/Kubernetes+Plugin?focusedCommentId=165577118=1539876104108#comment-165577118 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52487) p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Title: Message Title
Paul Allen updated an issue
Jenkins / JENKINS-52487
p4-plugin + global pipeline shared library - no ${JOB_NAME} expansion in view
Change By:
Paul Allen
Labels:
P4_VERIFY environment-variables pipeline
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22345) disk-usage-plugin causes jobs to hang at the end for 5min
Title: Message Title Todd B commented on JENKINS-22345 Re: disk-usage-plugin causes jobs to hang at the end for 5min I am seeing this exact problem. Is there a way too turn this off for certain jobs? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Badal Kotecha edited a comment on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin Hi [~jieshe], even with adding specific user and granting overall read permissions, when i keep the user id as Azure AD user id (i.e. email address) I am not able to invoke the API. It gives me 403 forbidden - Access Denied error indicating is missing the Overall/Read permission.Alternatively, When invoking the API with object id as the user id i get 500 Server error as indicated belowjava.lang.IllegalStateException: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@95ed46cf: Username: ; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@7798: RemoteIpAddress: 193.17.108.1; SessionId: null; Not granted any authoritiesCan you confirm it works for individual user at least? (not the group) and if I am missing anything? Note: I am using *Azure Active Directory Matrix-based security* This was working with Object ID as the user ID before I upgraded Azure AD plug-in but as per your suggestion when I updated the plugin and restarted the jenkins service (and even the VM), its not working either waysInterestingly, after further investigation the reason why it works is because anonymous user is granted an admin permission earlier. I realized this after removing Azure AD configuration from manage global security and re-configured everything from scratch. By default anonymous user is granted an admin permission, the moment I remove it, even of individual user the remote API call (despite of having overall read permissions), gives forbidden error. For sake of trying I turned on overall read permissions for Anonymous (not admin) and it started working again.. so granting permissions for individual users does not have any impact, you need to grant permissions to anonymous users to have overall read permissions. I think its a bug !! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Badal Kotecha edited a comment on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin Hi [~jieshe], even with adding specific user and granting overall read permissions, when i keep the user id as Azure AD user id (i.e. email address) I am not able to invoke the API. It gives me 403 forbidden - Access Denied error indicating is missing the Overall/Read permission.Alternatively, When invoking the API with object id as the user id i get 500 Server error as indicated belowjava.lang.IllegalStateException: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@95ed46cf: Username: ; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@7798: RemoteIpAddress: 193.17.108.1; SessionId: null; Not granted any authoritiesCan you confirm it works for individual user at least? (not the group) and if I am missing anything?This was working with Object ID as the user ID before I upgraded Azure AD plug-in but as per your suggestion when I updated the plugin and restarted the jenkins service (and even the VM), its not working either ways Interestingly, after further investigation the reason why it works is because anonymous user is granted an admin permission earlier. I realized this after removing Azure AD configuration from manage global security and re-configured everything from scratch. By default anonymous user is granted an admin permission, the moment I remove it, even of individual user the remote API call (despite of having overall read permissions), gives forbidden error. For sake of trying I turned on overall read permissions for Anonymous (not admin) and it started working again.. so granting permissions for individual users does not have any impact, you need to grant permissions to anonymous users to have overall read permissions. I think its a bug !! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Badal Kotecha edited a comment on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin Hi [~jieshe], even with adding specific user and granting overall read permissions, when i keep the user id as Azure AD user id (i.e. email address) I am not able to invoke the API. It gives me 403 forbidden - Access Denied error indicating is missing the Overall/Read permission.Alternatively, When invoking the API with object id as the user id i get 500 Server error as indicated belowjava.lang.IllegalStateException: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@95ed46cf: Username: ; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@7798: RemoteIpAddress: 193.17.108.1; SessionId: null; Not granted any authoritiesCan you confirm it works for individual user at least? (not the group) and if I am missing anything? This was working with Object ID as the user ID before I upgraded Azure AD plug-in but as per your suggestion when I updated the plugin and restarted the jenkins service (and even the VM), its not working either ways Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Badal Kotecha commented on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin Hi Jie Shen, even with adding specific user and granting overall read permissions, when i keep the user id as Azure AD user id (i.e. email address) I am not able to invoke the API. It gives me 403 forbidden - Access Denied error indicating is missing the Overall/Read permission. Alternatively, When invoking the API with object id as the user id i get 500 Server error as indicated below java.lang.IllegalStateException: Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@95ed46cf: Username: ; Password: [PROTECTED]; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@7798: RemoteIpAddress: 193.17.108.1; SessionId: null; Not granted any authorities Can you confirm it works for individual user at least? (not the group) and if I am missing anything? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54071) EC2-plugin not spooling up stopped nodes
Title: Message Title Oliver Pereira commented on JENKINS-54071 Re: EC2-plugin not spooling up stopped nodes It just waits for the servers to respond but it works fine after rolling back to the PR252 version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54143) Cannot create new users in 2.138.2
Title: Message Title Daniel Beck commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 There's a known problem with the classic UI not showing error messages (JENKINS-52869), but this one is new to me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52661) P4 Plugin fails to parse changelog
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52661 P4 Plugin fails to parse changelog Change By: Paul Allen Labels: P4_VERIFY SAXParseException changelog p4changeeparser Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52679) p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-52679 p4 plugin with spec file( load workspace spec from file in perforce) is not updating the workspace specs Change By: Paul Allen Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54133) No ANSI coloring on slave agents in pipeline
Title: Message Title Jesse Glick commented on JENKINS-54133 Re: No ANSI coloring on slave agents in pipeline I forgot to mention that as in JENKINS-54081 it is likely possible to work around this (have not yet tried it) using the JVM option -Dorg.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.USE_WATCHING=false, or (do not try this at home!) by disabling the SECURITY-382 defense. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-53723 [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync Change By: Paul Allen Labels: P4_VERIFY Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54145) Removed dependencies are not removed from list of upstream projects
Title: Message Title Milan Konzal created an issue Jenkins / JENKINS-54145 Removed dependencies are not removed from list of upstream projects Issue Type: Improvement Assignee: Unassigned Components: maven-plugin Created: 2018-10-18 13:50 Environment: Jenkins 2.138.2 Maven Integration plugin 3.1.2 Priority: Minor Reporter: Milan Konzal After dependency tree changes in my project removed dependecies are not removed from the upstream projects. I was not able to find the possibility to simply clean the list of upstream projects. My workaround deactivate the Build whenever a SNAPSHOT dependency is built start a build activate again the Build whenever a SNAPSHOT dependency is built and start a build again. Please provide some information in the documentation, or some possibility to clean the list of upstream projects by user interface, or reflect such changes in the dependency tree automatically. Add Comment
[JIRA] (JENKINS-32681) Option to disable script security approval
Title: Message Title Jesse Glick commented on JENKINS-32681 Re: Option to disable script security approval I had this one Groovy script that I use in a job to trigger downstream jobs Note that if you are using Pipeline, this can be done much more simply and safely using the build step. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41428) Tool Location Configuration Removed when Configuring System
Title: Message Title Nick Jones commented on JENKINS-41428 Re: Tool Location Configuration Removed when Configuring System Yes – I just observed same behavior here. In our case, it was the MSBuild.exe locations (we're a .NET shop), so it's definitely specific to the vSphere plugin, not Git. We're using vSphere 2.18 and Jenkins 2.138.2 LTS. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54143) Cannot create new users in 2.138.2
Title: Message Title Oleg Nenashev commented on JENKINS-54143 Re: Cannot create new users in 2.138.2 Any system logs for the broken instance? CC Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54142) Refusing to marshal jenkins.plugins.publish_over.BPInstanceConfig for security reasons
Title: Message Title Oleg Nenashev commented on JENKINS-54142 Re: Refusing to marshal jenkins.plugins.publish_over.BPInstanceConfig for security reasons Dayanand Guddeti please provide the plugin versions. Most probably you use old plugins and hit JENKINS-48920 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54142) Refusing to marshal jenkins.plugins.publish_over.BPInstanceConfig for security reasons
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-54142 Refusing to marshal jenkins.plugins.publish_over.BPInstanceConfig for security reasons Change By: Oleg Nenashev Assignee: Devin Nusbaum Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
