[JIRA] (JENKINS-61375) Cannot disable CSRF
Title: Message Title John Rocha commented on JENKINS-61375 Re: Cannot disable CSRF For those of you that stumble upon this issue. It is resolved with a Jenkins configuration change. There may be other ways to resolve this, but this is how I resolved it. Configure remote machine remote machine to add a token Log on to Jenkins as the user that will execute the job (i.e. build user) Select People Select your user ID (i.e. build user). Select Configure Find the section titled API Token to add a token Select Add new Token Select Generate Copy the token and keep it. This is the only time the token will be in plain text for you to copy. Select [Save] to save the token with the user Configure calling machine's remote parameterized interface to use this token Log on to Jenkins on the calling machine Select Manage Jenkins. Select Configure System. Scroll down to the the section Parameterized Remote Trigger Configuration and find the entry for the remote machine you added a token to in the previous step. Change Authentication to Token Authentication. Set the User Name to the correct user (i.e. build user) Paste the copied token from the previous configuration into the API Token_ field. Select [Save] This should fix the remote parameter calls. It should now work even with CSRF enabled.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Hi Basil Crow, I made a mistake. It is working fine on Linux. That one system hadn't been restarted yet. It is working once I restarted with the plugin update you provided. Thank you for your patience. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.0.1586885580343%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Good Morning Basil Crow. I noticed that I am also having this problem on Linux systems even with your patch applied. How do you want me to proceed? Open a new JIRA or update this one? If updating, what information do you need? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9738.1586790840121%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha edited a comment on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Thank you for your patience and tutelage. I installed the incremental plugin. !installed.png .png ! And I can confirm that I know observe the expected timestamps. Thank you.Also, for my own education. How did you navigate from the #59 plugin link to the HPI link? I suspect that could be useful for me to learn/know for the future.Thanks again!Cheers. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9021.1586532720360%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Thank you for your patience and tutelage. I installed the incremental plugin. And I can confirm that I know observe the expected timestamps. Thank you. Also, for my own education. How did you navigate from the #59 plugin link to the HPI link? I suspect that could be useful for me to learn/know for the future. Thanks again! Cheers. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9019.1586532660097%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha updated an issue Jenkins / JENKINS-61843 Timestamp missing for trailing lines in view as plain text mode. Change By: John Rocha Attachment: installed.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9017.1586532600231%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Thank you for the instructions on uploading a plugin .hpi file. Next question. How do I get the timestamper .hpi file? You shared a link for jenkinsci/timestamper-plugin#59. What are the steps I do not to download a .hpi file from the link? I don't see any obvious way to do that from the link shared. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9013.1586531580161%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Hello Basil Crow, how do i "try the incremental build"? I looked at Jenkins and I don't see an update for the timestamper plugin, so I'm guessing this hasn't been released yet. How do I install your changes in order to test? Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9004.1586529540215%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. That sounds great Basil Crow. Is there anything more you need from me? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.8501.1586381280172%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. This is a freestyle job I don't think -Dtimestmper-consolenotes=true has been set. Where would this option reside. It is not being set from the CLI when jenkins is started (jenkins is not running as a service). Requested informtaion has been attached as buildFolder.7z A 7-zip archive Also, my company has some very strict rules for sharing of this information so I was very aggressive with the sensitization. Essentially all letters were changed to 'a' and all numbers were changed to '#'. If this doesn't work, I might be able to do less sanitizing. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha updated an issue Jenkins / JENKINS-61843 Timestamp missing for trailing lines in view as plain text mode. Change By: John Rocha Attachment: buildFolder.7z Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.8356.1586375340301%40Atlassian.JIRA.
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha created an issue Jenkins / JENKINS-61843 Timestamp missing for trailing lines in view as plain text mode. Issue Type: Task Assignee: Unassigned Components: timestamper-plugin Created: 2020-04-08 18:16 Environment: Widows 10 Jenkins 2.222.1 Timestamper 1.11.2 Labels: timestamp Priority: Major Reporter: John Rocha I upgrade Jenkins and it's plugins once a month, and 2 days ago, 04/06/2020 was that day. After upgrading plugins and Jenkins I noticed that the timestamper output isn't always working. The web 'console' view works. It shows timestamps all the way to the last line, for example: 2020-04-08 07:25:53 2020-04-08 07:25:53 TestCommon_32R.exe 2020-04-08 07:25:53 Build was aborted 2020-04-08 07:25:53 Archiving artifacts 2020-04-08 07:25:53 Triggering a new build of GetLogFile-Trigger 2020-04-08 07:25:53 Finished: FAILURE However if I select the "View as plain text" link the timestamps stop part way through the output, and the timestamps don't match the web 'console' output. This is illustrated below: 2020-04-08 07:25:53
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title John Rocha commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade Having the same problem. I update about once a month and after updating from 2.204 to 2.222 I see the same issue, but I'm on Windows systems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205618.158582599.7703.1586276760217%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title John Rocha updated an issue Jenkins / JENKINS-61779 Regression: Job stuck in queue waiting forever after upgrade Change By: John Rocha Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205618.158582599.7698.1586276700335%40Atlassian.JIRA.
[JIRA] (JENKINS-61375) Cannot disable CSRF
Title: Message Title John Rocha commented on JENKINS-61375 Re: Cannot disable CSRF Daniel Beck, What do you mean "Fix your client." I'm just using Jenkins plugins. I don't have a client. I have Jenkins on slave and Jenkins on master. Jenkins on master uses trigger remote paramaterized job, for that you give the slave hostname information, and the name of the Jenkins job to trigger and it works. What specifically are you referring to – fix client and HTTP Basic authentication? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205028.1583530066000.3118.1583765460135%40Atlassian.JIRA.
[JIRA] (JENKINS-61375) Cannot disable CSRF
Title: Message Title John Rocha created an issue Jenkins / JENKINS-61375 Cannot disable CSRF Issue Type: Task Assignee: Unassigned Attachments: image-2020-03-06-13-25-49-111.png Components: core Created: 2020-03-06 21:27 Environment: fedora-20 Jenkins ver. 2.223 Priority: Blocker Reporter: John Rocha I have: Jenkins 2.204.4 running on a Windows 10 machine Jenkins 2.223 running on a Fedora20 machine Jenkins 2.204.4 running on a Centos7 machine The windows machine triggers jobs on the Fedora20 and Centos7 machines Using the "Trigger a remote parameterized job" plugin. This plugin 'triggers' the appropriate job on the Fedora20 and Centos7 machines. The last time the Fedora20 job succesfully ran "CSRF protection was disabled". Fedora20's jenkins version was updated and now Fedora20 fails. The output also now shows that "CSRF protection is now enabled." The Centos7 machine still works, and has CSRF disabled. However, if I enable CSRF on Cento7 I get the failure. I attempted to disable CSRF on Fedora20, and the option is no longer there. It now looks like this: There is only one option setting the curmb issuer to "Default crumb issuer"
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title John Rocha commented on JENKINS-55106 Re: Build stuck on final "exit 0" Andy Lin, I didn't seem to notice it when I did simple compiles without parallel compilation. Although I honestly would expect there to be at least a 2 minute delay even if there is just one compile process. But I don't know. Good luck. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196167.1544451681000.2916.1581014160779%40Atlassian.JIRA.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title John Rocha commented on JENKINS-55106 Re: Build stuck on final "exit 0" Andy Lin, what scenario are you encountering this under? I had a similar problem when using MS Visual Studio on a slave. In my case the problem is that the slave waits for remote processes to close, and has a timeout of ~2 minutes per process. I found that I had parallel compiles enabled and 6 remote VS compile session on the slave. When it finished, those VS processes would not go away, and every 2 minutes jenknis would kill one of them. I learned that MS causes compile processes to stick around once they are started. The idea being that when a new compile is needed it can grab one of the idle processes. However, in my case Jenkins doesn't need/want any more compiles and is stuck waiting for the VS processes to go away. There is a flag that can be used at the command line that informs VS to not keep the processes alive. Details for this can be found in a similar issue I logged JENKINS-59400 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196167.1544451681000.2821.1581012060689%40Atlassian.JIRA.
[JIRA] (JENKINS-60912) Document how to use matrix combinations parameter from the CLI or another job
Title: Message Title John Rocha created an issue Jenkins / JENKINS-60912 Document how to use matrix combinations parameter from the CLI or another job Issue Type: Task Assignee: Unassigned Attachments: Select.PNG Components: matrix-combinations-parameter-plugin Created: 2020-01-29 22:30 Environment: Windows 10 Labels: matrix Priority: Major Reporter: John Rocha I have a multi-configuration job that has two axes: VS_VERSION and BIT_ARCH. I have a single matrix-combinations-parameter "Select" that allows the user to select the combination they want (this works great, I love this feature.) I now need the ability to trigger this job from another job, and select a specific instance to build (i.e. VS2017 and 32 bit) not the default which is everything. However, passing the axes, VS_VERSION and BIT_ARCH as parameters doesn't work. Moreover, passing a parameter for Select doesn't seem to work either. There doesn't seem to be any documentation to explain how to do this either. Please add documentation to explain how we would do this.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title
John Rocha commented on JENKINS-54472
Re: Pin build at Perforce Label does not support variable expansion
Hello Karl Wirth, I was able to get this to work with plugin 1.10.5 (I haven't tried for awhile, so it may work with earlier versions too). What I did was as follows:
Define a choice parameter: P4_LABEL, with string trimming enabled.
Set the Perforce field "Pin build at Perforce Label" to ${P4_LABEL}
With this I successfully synced to change set 34307 by entering a value of @34307. Moreover, if I enter nothing, using the default where P4_LABEL is now set to nothing, it correctly pulls latest as expected. I think this case can be closed. I don't know if there was a fix that went in from when I first reported or if it was a miss-configuration on my part... but it works now when I do as explained above.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.154144342.10076.1571356740150%40Atlassian.JIRA.
[JIRA] (JENKINS-59400) Jenkins slave nodes hangs for up to 12+ minutes after build phase completes
Title: Message Title John Rocha commented on JENKINS-59400 Re: Jenkins slave nodes hangs for up to 12+ minutes after build phase completes Root cause - User calling error I ran the script manually from the CLI and observed that the MSBuild.exe processes never went away. Ever. I Googled for this and found this stackoverflow description/solution If parallel compiles are enabled and used, the default is for the MSBuild.exe process to stay around so it can be re-used by future compiles. This seems to cause a problem with the remote jenkins build pools. The MSBuild.exe reuse/linger functionality can be disabled by passing /nr:false for the build process. When I added this flag it resolved my issue. This problem doesn't happen if I am building without a build pool (i.e. one jenkins node that does it's own compiles). It only occurs when I go to a master/slave-build-pool scenario. Then it occurs when building on the slave nodes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201957.1568680052000.2794.1570475280048%40Atlassian.JIRA.
[JIRA] (JENKINS-59400) Jenkins slave nodes hangs for up to 12+ minutes after build phase completes
Title: Message Title John Rocha commented on JENKINS-59400 Re: Jenkins slave nodes hangs for up to 12+ minutes after build phase completes Update: The issue doesn't always happen. It seems to depend upon what is being done in the job. For example, if the job is to update perforce there is no noticeable delay. If it's to do a simple compile using Visual Studio there doesn't seem to be a delay for that either. By simple compile I mean few objects that don't seem to trigger parallel compilation. When it does happen it appears to be with bigger Visual Studio builds that have parallel compilation enabled. Moreover, I've noticed that there may be multiple MSBuild.exe processes still running even after Jenkins reports "build.bat existing with success" For example, during my most recent reproduction, there were 5 MSBuild.exe processes lingering after Jenkins reported the script exited with success, but the build didn't return the final result until ~8m later. The MSBuild.exe processes would slowly go away one by one. Once all of the MSBuild.exe processes terminated, the Jenkins job reported it's final "Finished: SUCCESS" result. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201957.1568680052000.2781.1570474260054%40Atlassian.JIRA.
[JIRA] (JENKINS-57721) remote jobs view shows last known status when remote server is unreachable
Title: Message Title John Rocha commented on JENKINS-57721 Re: remote jobs view shows last known status when remote server is unreachable Any update for this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199664.1559067622000.5494.1568738940121%40Atlassian.JIRA.
[JIRA] (JENKINS-56340) Build-Publisher does not work with CloudBees Folders
Title: Message Title John Rocha commented on JENKINS-56340 Re: Build-Publisher does not work with CloudBees Folders Any update for this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197925.1551401236000.5488.1568738880235%40Atlassian.JIRA.
[JIRA] (JENKINS-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title John Rocha commented on JENKINS-54472 Re: Pin build at Perforce Label does not support variable expansion Any update on this issue? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195237.154144342.5486.1568738820098%40Atlassian.JIRA.
[JIRA] (JENKINS-59400) Jenkins slave nodes hangs for up to 12+ minutes after build phase completes
Title: Message Title John Rocha created an issue Jenkins / JENKINS-59400 Jenkins slave nodes hangs for up to 12+ minutes after build phase completes Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-17 00:27 Environment: * Jenkins 2.176.2 * Master(x1) and Build(x6) nodes are running Windows 10 64B Enterprise * Java Version 8 Update 201 (build 1.8.0_201-b09) Oracle * Jenkins is running on Master from command line call * Jenkins is running on Slaves as a service * Web browser: Chrome Version 76.0.3809.132 (Official Build) (64-bit) Labels: slave slaves Slave hang hanging delay Priority: Critical Reporter: John Rocha Jenkins slave nodes hangs for up to 12+ minutes after build phase completes. I have a master node and 7 nodes in the build pool. The master is configured to only run jobs labeled master. Builds are always only done from the build nodes. There are no post-build steps configured. Hang/delay is observed if the build step passes and/or fails. Example Console Output follows --- 2019-09-16 16:51:45 ERROR: last command returned failure: 1 2019-09-16 16:51:45 2019-09-16 16:51:45 build.bat failed
[JIRA] (JENKINS-58833) NodeLabel Parameter Plugin does not work for concurrent
Title: Message Title John Rocha created an issue Jenkins / JENKINS-58833 NodeLabel Parameter Plugin does not work for concurrent Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 2019-08-06 18:55 Environment: Jenkins 2.176.2 Windows 10 Internet Explorer, Firefox, Chrome Plugin version 1.72 Priority: Critical Reporter: John Rocha I created a project to run on agents. The project causes the agent's workspace to be updated with the latest from Perforce (SCM software). The project has: Allow multi node selection for concurrent builds configured Execute concurrent builds if necessary configured. Restrict whre this project can be run disabled. Master has 8 executors, slaves have 1 executor If I select master, node1 and node2 - only master runs. All should run. If I select node1 and node - node 1 runs, and once that finishes node2 runs. node1 and node2 should run at the same time on the two agent nodes.
[JIRA] (JENKINS-57721) remote jobs view shows last known status when remote server is unreachable
Title: Message Title John Rocha created an issue Jenkins / JENKINS-57721 remote jobs view shows last known status when remote server is unreachable Issue Type: Bug Assignee: Jeff Horan Components: remote-jobs-view-plugin Created: 2019-05-28 18:20 Environment: Windows and Linux Jenkins version 2.164.2 Priority: Major Reporter: John Rocha The remote view plugin shows the last reported job status when a server is unreachable. The remote view plugin should instead show that the remote server is unreachable. This causes reporting confusion. We have a scenario where the last cached result was pass, then the server went offline. It was several days before the administrator learned that the Jenkins instance on the remote server stopped because the remote view was showing the cached pass results instead of unreachable. Add Comment
[JIRA] (JENKINS-56550) Credentials fail if password has dollar sign ($) in it
Title: Message Title John Rocha created an issue Jenkins / JENKINS-56550 Credentials fail if password has dollar sign ($) in it Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2019-03-13 21:20 Environment: Windows 8.1 Jenkins 2.150.3 Priority: Major Reporter: John Rocha Using Credentials with the Parameterized Remote Trigger plugin. Created Credentials Scope Global Username build Password $SecretP@ssword ID Default
[JIRA] (JENKINS-56340) Build-Publisher does not work with CloudBees Folders
Title: Message Title John Rocha created an issue Jenkins / JENKINS-56340 Build-Publisher does not work with CloudBees Folders Issue Type: Improvement Assignee: vjuranek Components: build-publisher-plugin Created: 2019-03-01 00:47 Environment: build-publisher: 1.22 jenkins: 2.150.3 Priority: Major Reporter: John Rocha I use the CloudBees Folders pluging to keep jobs clean. Similar jobs are kept together. When I create a job under a cloud be folder, and it has the post-build step of publishing nothing happens. If I move the job from the folder to the top level Jenkins location, then it works. For example: Install Folders pluging Create Folder Foo Create job in folder Foo-Job that has a post-build action of publishing to another jenkins instance Execute Foo-job The job runs but no publishing is attempted. Move the job from Folder Foo to the top level location Execute Foo-job from new location The job runs and now Build Publisher Status shows an attempt at publishing In this scenario, I have a Private job running on Windows 10 and Public job on a Scientific Linux. They both have the same version of Build-Publisher
[JIRA] (JENKINS-30843) Jobs that are in (CloudBees) folders cannot be selected to the view.
Title: Message Title John Rocha commented on JENKINS-30843 Re: Jobs that are in (CloudBees) folders cannot be selected to the view. I just found this plugin and noticed that it only shows jobs at the "top level." If we add a folder using the "CloudBees Folders Plugin" https://wiki.jenkins.io/display/JENKINS/CloudBees+Folders+Plugin Only the name of the folder is displayed, we are not able to view the jobs inside the folder. Also don't forget jobs inside of folders that are inside other folders. 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-54472) Pin build at Perforce Label does not support variable expansion
Title: Message Title
John Rocha created an issue
Jenkins / JENKINS-54472
Pin build at Perforce Label does not support variable expansion
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-11-05 18:43
Environment:
CentOS-7 (Linux CentOS-7 3.10.0-862.14.4.el7.x86_64 #1 SMP Wed Sep 26 15:12:11 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux) Jenkins war (org.jenkins-ci.main:jenkins-war:2.138.2) P4 Plugin (1.9.3)
Labels:
p4 p4plugin P4_PLUGIN
Priority:
Major
Reporter:
John Rocha
The description for the "Pin a build at Perforce Label" indicates the following:
When a build is triggered by Polling, Build Now or an external Action, the workspace will sync only to the specified label. Any other specified change or label will be ignored.
Supports variable expansion e.g. ${VAR}. If 'now' is used, or a variable that expands to 'now', then the latest change is used (within the scope of the workspace view).
This is not working. I tried ${SV_P4_CHANGELOG} where the value was not set, and hence is empty, and the tool is looking for the label SV_P4_CHANGELOG, as shown below
[JIRA] (JENKINS-54195) Add support for p4 clean
Title: Message Title John Rocha created an issue Jenkins / JENKINS-54195 Add support for p4 clean Issue Type: Improvement Assignee: Unassigned Components: p4-plugin Created: 2018-10-22 21:18 Priority: Minor Reporter: John Rocha I would like to have the ability to invoke 'p4 clean'. I want my workspace cleaned of all files that are not part of the repo. So I start fresh again, but without doing a 'get latest.' We have a build environment where we will build for 32B, and then our quality process requires that the workspace be reset/cleaned and then build for 64B. I do not want to do a sync and clean, because new commits could have occurred after the 32B started, meaning a sync and clean just before 64B would pull in new changes and and they would not contain the same contents. Add Comment
