[JIRA] (JENKINS-61935) Declarative Syntax Generator gives wrong format for timestamps option
Title: Message Title
Ken Rachynski created an issue
Jenkins / JENKINS-61935
Declarative Syntax Generator gives wrong format for timestamps option
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-04-16 20:38
Environment:
Jenkins 2.222.1, all plugins up to date
Priority:
Minor
Reporter:
Ken Rachynski
With a pipeline job configured, go to the declarative directive generator. Pick `options` and add `timestamps`. The generated syntax is options { timestamps } However, the documentation clearly states (in the example only, though) that the format should be options { timestamps() }
Add Comment
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Ken Rachynski commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing Oh good catch. I have jglick as one of my users and I recall that's because I built his sample pipeline job from github directly. The unknown user in my case is one of our current staff members, but it's likely that record was added before I switched to Active Directory as my source. 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.193341.1535412226000.9188.1574981520482%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Ken Rachynski commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing As near as I can tell right now, the Revoke selected token(s) button calls this method: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/apitoken/LegacyApiTokenAdministrativeMonitor.java#L159-L185 But none of the logging present there seems to be hitting my Jenkins logs. 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.193341.1535412226000.9132.1574969820388%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title
Ken Rachynski edited a comment on JENKINS-53266
Re: Legacy token for user "unknown" keeps reappearing
Since I suspect this is due to a plugin upgrade at some point, I decided to do some digging. It looks like revoking legacy tokens for some users isn't actually revoking them. I have one unknown user on my system that shows up every time I restart Jenkins. I've been revoking the token each time it comes up without luck.Logging into my Jenkins host computer, I looked in the users folder for my unknown user. users.xml told me what directory it was in and the config.xml confirmed the legacy token.{{ }} {{ tokenhash }} {{ }}The new format looks more like{{ }} {{ }} {{ }} {{ }} {{ uuid }} {{ mytoken }} {{ 2019-11-28 18:37:11.655 UTC }} {{ }} {{ 11 }} {{ tokenhash }} {{ }} {{ }} {{ }} {{ }} {{ }}Since I was looking to revoke the token outright, I just deleted the {{}} line in config.xml and restarted Jenkins.
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.193341.1535412226000.9111.1574967120583%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title
Ken Rachynski commented on JENKINS-53266
Re: Legacy token for user "unknown" keeps reappearing
Since I suspect this is due to a plugin upgrade at some point, I decided to do some digging. It looks like revoking legacy tokens for some users isn't actually revoking them. I have one unknown user on my system that shows up every time I restart Jenkins. I've been revoking the token each time it comes up without luck. Logging into my Jenkins host computer, I looked in the users folder for my unknown user. users.xml told me what directory it was in and the config.xml confirmed the legacy token. {{ tokenhash }} The new format looks more like {{ uuid mytoken 2019-11-28 18:37:11.655 UTC 11 tokenhash }} Since I was looking to revoke the token outright, I just deleted the line in config.xml and restarted Jenkins.
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.193341.1535412226000.9096.1574966940448%40Atlassian.JIRA.
[JIRA] (JENKINS-53266) Legacy token for user "unknown" keeps reappearing
Title: Message Title Ken Rachynski commented on JENKINS-53266 Re: Legacy token for user "unknown" keeps reappearing I can suggest three more removals from Filipe Roque's list. I do not have Build Pipeline Plugin, Dashboard View, or Pipeline Graph Analysis Plugin on the server where I'm seeing this behaviour. I set up a Docker instance and added most of my production plugins in by hand and have not been able to reproduce this behaviour yet. I say most because I have a NCover plugin in production that doesn't seem to exist any more. As I haven't been able to reproduce this empty token issue, I'm beginning to suspect that this is due to an upgrade somewhere along the lines. 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.193341.1535412226000.9081.1574964540516%40Atlassian.JIRA.
[JIRA] (JENKINS-50640) Link messages together
Title: Message Title Ken Rachynski created an issue Jenkins / JENKINS-50640 Link messages together Issue Type: New Feature Assignee: Srivardhan Hebbar Attachments: Screen Shot 2018-04-06 at 10.39.57 AM.png Components: office-365-connector-plugin Created: 2018-04-06 16:44 Priority: Minor Reporter: Ken Rachynski I am wondering if it would be possible to link messages together such that all statuses for a single build are shown as a single message thread in Teams. So that Starting, Failed/Unstable/Success are together. Currently each message starts its own conversation as seen in the attached image. Add Comment
[JIRA] (JENKINS-46408) Display full job name
Title: Message Title
Ken Rachynski commented on JENKINS-46408
Re: Display full job name
I just updated my central notification call and noticed this very thing. I worked around it by including ${env.JOB_NAME} in the message: call, but having the bold subject of the Teams message have the JOB_NAME would be a lot better.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46408) Display full job name
Title: Message Title Ken Rachynski updated an issue Jenkins / JENKINS-46408 Display full job name Change By: Ken Rachynski Attachment: Screen Shot 2018-04-06 at 10.39.57 AM.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50301) [JDK9] Java WebStart Unsupported past Java 8
Title: Message Title Ken Rachynski created an issue Jenkins / JENKINS-50301 [JDK9] Java WebStart Unsupported past Java 8 Issue Type: New Feature Assignee: Unassigned Components: core Created: 2018-03-20 17:41 Priority: Minor Reporter: Ken Rachynski Oracle has stated that Java WebStart will not be supported past Java SE 8. This may affect launching Agents manually via JNLP. http://www.oracle.com/technetwork/java/eol-135779.html Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-49211) Build gets stuck on Publish Over CIFS
Title: Message Title Ken Rachynski commented on JENKINS-49211 Re: Build gets stuck on Publish Over CIFS I did have a chance to speak with one of the updaters on IRC and he acknowledged this issue but is currently working on security tasks. The workaround for now is to downgrade. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24846) UI Improvement: Update Center
Title: Message Title Ken Rachynski commented on JENKINS-24846 Re: UI Improvement: Update Center Alternative I've been going to the Available Plugins tab to find the Check Now button. It would be nice to see that on the Updates tab as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31247) Copyartifact: more integration with workflow
Title: Message Title Ken Rachynski commented on JENKINS-31247 Re: Copyartifact: more integration with workflow I was just looking for this functionality in 1.38.1 and see that this request has been idle for just over a year. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-33712) Empty parameterized build properties not quoted when passed to ant
Title: Message Title Ken Rachynski commented on JENKINS-33712 Re: Empty parameterized build properties not quoted when passed to ant I can report that I upgraded my LTS system and ant builds are running properly with 1.3. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-33712) Empty parameterized build properties not quoted when passed to ant
Title: Message Title Ken Rachynski commented on JENKINS-33712 Re: Empty parameterized build properties not quoted when passed to ant I just encountered this bug this week after upgrading my LTS installation to 1.651.1. Rolling back to LTS 1.642.4 fixed the issue for me, but LTS is supposed to be stable, eh? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials-plugin] (JENKINS-20637) SSH Keys are only usable on master, not replicated on slaves
Title: Message Title Ken Rachynski commented on JENKINS-20637 Re: SSH Keys are only usable on master, not replicated on slaves master is Server 2008, slave is 2012 r2 Git 2.7.3 installed Slave started as a JNLP service process using a domain account Credentials are defined for ssh private key only I'll have to look up the service bug, I guess Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-credentials-plugin] (JENKINS-20637) SSH Keys are only usable on master, not replicated on slaves
Title: Message Title Ken Rachynski commented on JENKINS-20637 Re: SSH Keys are only usable on master, not replicated on slaves I have been seeing this behaviour lately when using local installs of Git on Windows slaves. Switching to jgit will allow the credentials to pass properly to the slave for use. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-30094) Build monitor blank
Title: Message Title Ken Rachynski created an issue Jenkins / JENKINS-30094 Build monitor blank Issue Type: Bug Assignee: Unassigned Components: build-monitor-plugin Created: 21/Aug/15 8:55 PM Environment: jenkins 1.622, build-monitor-plugin 1.6+build.150, build-failure-analyzer-plugin 1.13.0, claim-plugin 2.7 Priority: Minor Reporter: Ken Rachynski This may be related to JENKINS-28102. I was trying to tune up failure searches in the build-failure-analyzer today and noticed that my build-monitor views stopped working in that they were showing the header, footer and background, but no actual job tiles. Looking into the logs, it appears that build-monitor is trying to invoke build-failure-analyzer and failing to find it. I may try removing build-failure-analyzer to see if that fixes build-monitor, but I'll wait on your advice first in case you can think of something else I can look at to troubleshoot. Log follows: Aug 21, 2015 2:15:41 PM WARNING org.kohsuke.stapler.HttpResponseRenderer$Default handleJavaScriptProxyMethodCall call to /$stapler/bound/0ebc8003-0cb7-4441-a764-599414a716b4/fetchJobViews failed java.lang.NoClassDefFoundError:
