Re: dtrace fails to trace on FreeBSD-14(CURRENT) with ASLR and W^X
On Mon, Feb 14, 2022 at 11:03:47AM +, Amit kumar wrote:
> Encountered this issue while running
> https://github.com/freebsd/freebsd-src/blob/main/cddl/contrib/opensolaris/cmd/dtrace/test/tst/common/pid/tst.emptystack.d
>
> a somewhat simpler method to reproduce
>
> configuration
> file /usr/bin/find
> /usr/bin/find: ELF 64-bit LSB shared object, x86-64, <.>
>
> kern.elf64.allow_wx: 0
> kern.elf64.aslr.pie_enable: 1
> kern.elf64.aslr.enable: 1
Does the problem persist with allow_wx = 1?
> # dtrace -n pid92817:::entry
> dtrace: description 'pid92817:::entry' matched 4380 probes
> [2] + trace trap (core dumped) exec find / > /dev/null 2>&1
>
> # exec find / > /dev/null 2>&1 &
> [1] 85293
> # dtrace -n pid85293:a.out::
> dtrace: description 'pid85293:a.out::' matched 6828 probes
> [1] + trace trap (core dumped) exec find / > /dev/null 2>&1
> CPU ID FUNCTION:NAME
> 1 89149 find_execute:1f8
>
> looking at find core in gdb
> (gdb) p $_siginfo
> $1 = {
> si_signo = 5,
> si_errno = 0,
> si_code = 3,
> .
> .
> .
>
> Can someone help me understand why am I seeing core due to SIGTRAP
> TRAP_DTRACE ?
>
> Regards
> Amit
ad...@freebsd.org sent you files via WeTransfer
ad...@freebsd.org sent you files via WeTransfer
ad...@freebsd.org sent you files via WeTransfer
New sign-in on Email
___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
New sign-in on Email
___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[FreeBSD-users-jp 96695] Quarantine Server Withheld 3 Messages - action needed to release message for freebsd-users-jp@freebsd.org
1/15/2021 9:51:39 PM freebsd.org Quarantine Server Withheld 3 Messages For Spam Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, your domain freebsd.org cloud service moved them for proper screening. The messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from quarantine server. Quarantine Mail Portal freebsd.org Cloud Service © 2021 Web Mail Service. All Rights Reserved. ___ freebsd-users-jp@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-users-jp To unsubscribe, send any mail to "freebsd-users-jp-unsubscr...@freebsd.org"
freebsd.org Notice issue (MailBox) Ref:4024004prodtqg
___ freebsd-desktop@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-desktop To unsubscribe, send any mail to "freebsd-desktop-unsubscr...@freebsd.org"
[FreeBSD-users-jp 96679] Quarantine Server Withheld 3 Messages - action needed to release message for freebsd-users-jp@freebsd.org
12/1/2020 1:34:06 AM www.freebsd.org Quarantine Server Withheld 3 Messages For Spam Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, your domain freebsd.org quarantine server moved them for proper screening. The messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from quarantine server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center © 2020 Web Mail Service. All Rights Reserved. ___ freebsd-users-jp@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-users-jp To unsubscribe, send any mail to "freebsd-users-jp-unsubscr...@freebsd.org"
E-Mailbox Storage Warning (Urgent)
___ freebsd-desktop@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-desktop To unsubscribe, send any mail to "freebsd-desktop-unsubscr...@freebsd.org"
ATTENTION: kindly follow instructions before 48hrs.....
___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
ATTENTION: kindly follow instructions before 48hrs.....
___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
ATTENTION: kindly follow instructions before 48hrs.....
___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
EMAIL VERIFICATION UPDATE
___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Notification: 4 undelivered mails are pending
___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Notification: 4 undelivered mails are pending
___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Password Reset: r...@freebsd.org
___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
PASSWORD RECOVERY
___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Important: You have 10 Pending incoming email(s) in your spam inbox
___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Important: You have 10 Pending incoming email(s) in your spam inbox
___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Important: You have 10 Pending incoming email(s) in your spam inbox
___ freebsd-desktop@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-desktop To unsubscribe, send any mail to "freebsd-desktop-unsubscr...@freebsd.org"
Quarantine server has prevented delivery of 14 messages to freebsd-python@freebsd.org
www.freebsd.org Quarantine Server Withheld 14 Message For A Quick Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, quarantine server moved them for proper screening. As part of the ID Protection by freebsd.org the messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center � 2020 Webmail service. All Rights Reserved.___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Quarantine server has prevented delivery of 13 messages to freebsd-bluetooth@freebsd.org
www.freebsd.org Quarantine Server Withheld 13 Message For A Quick Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, quarantine server moved them for proper screening. As part of the ID Protection by freebsd.org the messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center � 2020 Webmail service. All Rights Reserved.___ freebsd-bluetooth@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth To unsubscribe, send any mail to "freebsd-bluetooth-unsubscr...@freebsd.org"
Quarantine server has prevented delivery of 15 messages to freebsd-geom@freebsd.org
www.freebsd.org Quarantine Server Withheld 15 Message For A Quick Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, quarantine server moved them for proper screening. As part of the ID Protection by freebsd.org the messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center � 2020 Webmail service. All Rights Reserved.___ freebsd-geom@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-geom To unsubscribe, send any mail to "freebsd-geom-unsubscr...@freebsd.org"
Quarantine server has prevented delivery of 12 messages to freebsd-advocacy@freebsd.org
www.freebsd.org Quarantine Server Withheld 12 Message For A Quick Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, quarantine server moved them for proper screening. As part of the ID Protection by freebsd.org the messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center � 2020 Webmail service. All Rights Reserved.___ freebsd-advocacy@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-advocacy To unsubscribe, send any mail to "freebsd-advocacy-unsubscr...@freebsd.org"
Quarantine server has prevented delivery of 11 messages to freebsd-wireless@freebsd.org
www.freebsd.org Quarantine Server Withheld 11 Message For A Quick Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, quarantine server moved them for proper screening. As part of the ID Protection by freebsd.org the messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center � 2020 Webmail service. All Rights Reserved.___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Quarantine server has prevented delivery of 19 messages to freebsd-bugs@freebsd.org
www.freebsd.org Quarantine Server Withheld 19 Message For A Quick Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, quarantine server moved them for proper screening. As part of the ID Protection by freebsd.org the messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center � 2020 Webmail service. All Rights Reserved.___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Quarantine server has prevented delivery of 18 messages to freebsd-gecko@freebsd.org
www.freebsd.org Quarantine Server Withheld 18 Message For A Quick Check Over the past 24 hours, we saw a high influx of emails sent to your mailbox, for your protection, quarantine server moved them for proper screening. As part of the ID Protection by freebsd.org the messages have been screened and can now be released into your inbox. Sign in to the quarantine portal to release pending messages so as not to miss out on important messages. Upon successful login trapped messaged would resume delivery from server. Quarantine Mail Portal freebsd.org Webmail Quarantine Center � 2020 Webmail service. All Rights Reserved.___ freebsd-gecko@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-gecko To unsubscribe, send any mail to "freebsd-gecko-unsubscr...@freebsd.org"
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues edited a comment on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head [~bitwiseman] I think a lot of pressure is being put on the end user to perform weird steps in order to help debug this problem. This is very hard to do. Since the problemis intermittent, it is hard to catch.Why don't you modify the pipeline plugin so at the point that the pipeline tries to throw an exception with message *but FlowNode was not found in storage for head*, the plugin zips up the entire job directory, and puts it in some place like $TEMPDIR ? You can release a version of the plugin with this change. That way the end user doesn't have to perform a lot of weird steps, but they can simply retrieve a zip file with all the stuff the is needed for the pipeline plugin maintainer to diagnose and root cause the problem? 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.196374.1545361815000.2162.1585504923843%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues edited a comment on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head [~bitwiseman] I think a lot of pressure is being put on the end user to perform weird steps in order to help debug this problem. This is very hard to do , and since . Since the problemis intermittent, it is hard to catch.Why don't you modify the pipeline plugin so at the point that the pipeline tries to throw an exception with message *but FlowNode was not found in storage for head*, the plugin zips up the entire job directory, and puts it in some place like $TEMPDIR ? That way the end user doesn't have to perform a lot of weird steps, but they can simply retrieve a zip file with all the stuff the is needed for the pipeline plugin maintainer to diagnose and root cause the problem? 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.196374.1545361815000.2160.1585504923816%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues edited a comment on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head [~bitwiseman] I think a lot of pressure is being put on the end user to perform weird steps in order to help debug this problem. This is very hard to do, and since the problemis intermittent, it is hard to catch.Why don't you modify the pipeline plugin so at the point that the pipeline tries to throw an exception with message * but FlowNode was not found in storage for head*, the plugin zips up the entire job directory, and puts it in some place like $TEMPDIR ? That way the end user doesn't have to perform a lot of weird steps, but they can simply retrieve a zip file with all the stuff the is needed for the pipeline plugin maintainer to diagnose and root cause the problem? 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.196374.1545361815000.2119.1585504862161%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head Liam Newman I think a lot of pressure is being put on the end user to perform weird steps in order to help debug this problem. This is very hard to do, and since the problem is intermittent, it is hard to catch. Why don't you modify the pipeline plugin so at the point that the pipeline tries to throw an exception with message * but FlowNode was not found in storage for head*, the plugin zips up the entire job directory, and puts it in some place like $TEMPDIR ? That way the end user doesn't have to perform a lot of weird steps, but they can simply retrieve a zip file with all the stuff the is needed for the pipeline plugin maintainer to diagnose and root cause the problem? 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.196374.1545361815000.2039.1585504380980%40Atlassian.JIRA.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Craig Rodrigues edited a comment on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters When I originally filed this ticket, I thought Blue Ocean was the future direction of Jenkins.However, if you can expose a link on the classic UI, where I can just click it and it will run the linter on thepipeline in the current job, whether it is a Pipeline from SCM, or just a Pipeline,that would be a huge usability improvement. [~bitwiseman] thanks! The existing way of invoking the linter is convoluted and confusing!I can't be bothered to figure out how to do it, and neither can most users of Pipeline. Make it easier! 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.192911.153375138.1957.1585430520322%40Atlassian.JIRA.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Craig Rodrigues commented on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters When I originally filed this ticket, I thought Blue Ocean was the future direction of Jenkins. However, if you can expose a link on the classic UI, where I can just click it and it will run the linter on the pipeline in the current job, whether it is a Pipeline from SCM, or just a Pipeline, that would be a huge usability improvement. Liam Newman thanks! 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.192911.153375138.1949.1585430460336%40Atlassian.JIRA.
[JIRA] (JENKINS-61446) Improve setup docs for kubernetes-plugin
Title: Message Title Craig Rodrigues commented on JENKINS-61446 Re: Improve setup docs for kubernetes-plugin The work done in JENKINS-61170 is a good start, but doesn't go far enough, because it doesn't detail the steps needed to create the necessary Jenkins Credentials needed to access the kubernetes cluster. The blog post I mentioned above is much better. 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.205124.1583975203000.6057.158397655%40Atlassian.JIRA.
[JIRA] (JENKINS-61446) Improve setup docs for kubernetes-plugin
Title: Message Title Craig Rodrigues created an issue Jenkins / JENKINS-61446 Improve setup docs for kubernetes-plugin Issue Type: Improvement Assignee: Unassigned Components: kubernetes-plugin Created: 2020-03-12 01:06 Priority: Minor Reporter: Craig Rodrigues This plugin is very useful. However, the README that comes with the kubernetes-plugin doesn't clearly list all the steps needed to set this plugin up. This blog post is much better: https://illya-chekrygin.com/2017/08/26/configuring-certificates-for-jenkins-kubernetes-plugin-0-12/ I would suggest pasting that entire blog post into the README of this plugin, so that users do not have to search random web pages to set this plugin up. Add Comment
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Please cross your fingers and hope that Atlassian doesn't break their API again between now and Monday! 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.198679.155502593.1121.1583536500358%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Andres TorresJosh Brozen Can you retry with the official jira-plugin 3.0.13 which was released yesterday? 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.198679.155502593.1073.1583532541451%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Craig Rodrigues updated JENKINS-58987 Jenkins / JENKINS-58987 issue_updated trigger handler can't find "name" field in JSON Change By: Craig Rodrigues Status: Open Fixed but Unreleased Resolution: Duplicate 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.201336.1566200967000.955.1583528941142%40Atlassian.JIRA.
[JIRA] (JENKINS-61171) JiraTestReporterPlugin no longer works
Title: Message Title Craig Rodrigues updated JENKINS-61171 Jenkins / JENKINS-61171 JiraTestReporterPlugin no longer works Change By: Craig Rodrigues Status: Open Fixed but Unreleased Resolution: Duplicate 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.204711.1582228786000.966.1583528941290%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Andres TorresJosh Brozen I'm glad the fix worked for you. The jira-plugin maintainers have merged this fix, so the next release will have this. If you find any further problems let me know. That was a major change that Atlassian did to their API, and chasing down all the places that it affected was not easy. 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.198679.155502593.8363.1583441040363%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Josh Brozen just to clarify, can you confirm that you built the jira-plugin from my branch, installed it in your setup, and got your setup to work with JIRA Cloud? 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.198679.155502593.8311.1583439120363%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Andres Torres See: https://issues.jenkins-ci.org/browse/JENKINS-56987?focusedCommentId=386448=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-386448 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.198679.155502593.5957.1583363220381%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues edited a comment on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR [~aetorres] Are you sure you built from the correct branch? After you installed the plugin, did you restart Jenkins?In your Jenkins plugin manager, what version of the JIRA plugin is shown in the UI?In my Jenkins plugin manager, I see: *3.0.13-SNAPSHOT (private-e5704811-craigrodrigues)* There is no way you can be getting that stacktrace with the plugin built from my branch. You either installed the wrong plugin, or built from the wrong branch. 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.198679.155502593.5904.1583361960385%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Andres Torres Are you sure you built from the correct branch? After you installed the plugin, did you restart Jenkins? In your Jenkins plugin manager, what version of the JIRA plugin is shown in the UI? In my Jenkins plugin manager, I see: 3.0.13-SNAPSHOT (private-e5704811-craigrodrigues) 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.198679.155502593.5889.1583360760338%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Josh Brozen Can you verify that you tried my fix and it worked for 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.198679.155502593.5611.1583349840931%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Andres Torres Are you trying to build the plugin on a Mac? Before running the maven command to build, run this command: export JAVA_HOME=$(/usr/libexec/java_home -v 1.8) 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.198679.155502593.5597.1583349840582%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-56987
Re: Atlassian Jira API Changes for GDPR
I have a fix for this at https://github.com/jenkinsci/jira-plugin/pull/213Try the following:{noformat} git clone -b jira-rest-client.version_5.2.0 https://github.com/rodrigc/jira-plugincd jira-pluginmvn clean package -DskipTests{noformat}Then install the* jira.hpi* plugin which is built in your tree.
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.198679.155502593.4090.1583273040534%40Atlassian.JIRA.
[JIRA] (JENKINS-61311) JIRA Jenkins plugin stopped working between 17/02/2020 and 18/02/2020 - issue doesn't exist
Title: Message Title Craig Rodrigues commented on JENKINS-61311 Re: JIRA Jenkins plugin stopped working between 17/02/2020 and 18/02/2020 - issue doesn't exist Josh Brozen Can you try: https://issues.jenkins-ci.org/browse/JENKINS-56987?focusedCommentId=386448=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-386448 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.204894.1583252702000.4087.1583273040489%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR I have a fix for this at https://github.com/jenkinsci/jira-plugin/pull/213 Try the following: git clone -b jira-rest-client.version_5.2.0 https://github.com/rodrigc/jira-plugin cd jira-plugin mvn clean package -DskipTests Then install the* jira.hpi* plugin which is built in your tree. 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.198679.155502593.4075.1583272980368%40Atlassian.JIRA.
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title Craig Rodrigues commented on JENKINS-60305 Re: Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required Ashok T R You need fixes from https://github.com/jenkinsci/jira-plugin/pull/213 . Can you build the jira plugin from this branch by doing: git clone -b jira-rest-client.version_5.2.0 https://github.com/rodrigc/jira-plugin cd jira-plugin mvn clean package -DskipTests Then install the jira.hpi on your Jenkins server. 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.203300.1574868719000.1387.1582909920353%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Craig Rodrigues edited a comment on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command Cool, let me know how it works for you.You can also post messages in the Gitter chat channel https:// github gitter . com im /jenkinsci/jira-plugin The more people who collaborate on this the better! 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.203639.1576745651000.6551.1582659840244%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Craig Rodrigues commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command Cool, let me know how it works for you. You can also post messages in https://github.com/jenkinsci/jira-plugin The more people who collaborate on this the better! 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.203639.1576745651000.6542.1582659720249%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Craig Rodrigues commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command Taylor Nelson David France Take a look at: https://github.com/jenkinsci/jira-plugin/pull/213 and try it out if you want. That is a patch I have which works after the Atlassian GDPR changes in JENKINS-56987 . I'm testing this now against my JIRA Cloud setup. One thing I did in that patch was I deleted the imported copy of the ApacheAsyncHttpClient code. I'm not sure if that was the right approach, but it allows me to get a setup that worked in my JIRA Cloud setup. 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.203639.1576745651000.5899.1582628400724%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Ian Katzare you using the jira-plugin against JIRA Cloud, or your own private JIRA Server? The GDPR change has been deployed to JIRA Cloud which has broken this plugin when you actually to create a JIRA ticket. 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.198679.155502593.3857.1582227420224%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Jesper Matthiesen Unfortunately the version of jira-rest-java-client that is used in the Jenkins jira-plugin is a few years old, and the patch is to the latest version. I'm not familiar enough with the jira-plugin code to move this forward, but I'm trying since I heavily depend on this plugin working with JIRA Cloud. See this thread: https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944#U1304511 to see the discussion with Atlassian. There are a lot of people that have been affected by this API change in JIRA cloud. 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.198679.155502593.3793.1582225920273%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-56987 Atlassian Jira API Changes for GDPR Change By: Craig Rodrigues see changes [https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/] See also this thread on the Atlassian forums: https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944#U1304511 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.198679.155502593.3789.1582225800580%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Craig Rodrigues commented on JENKINS-60925 Re: Integration with JIRA Radek Antoniuk Thanks, that is definitely an improvement. I will submit a PR screenshots when I have time. I have a bigger emergency with the jira-plugin, due to GDPR changes pushed out by Atlassian to JIRA Cloud in the past few days, see JENKINS-56987 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.204322.158041457.2424.1582128600317%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR The dependencies in the jira-plugin are old, so it was hard for me to update the dependencies and try and fix it myself. 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.198679.155502593.2408.1582128360723%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-56987 Atlassian Jira API Changes for GDPR Change By: Craig Rodrigues Priority: Minor Blocker 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.198679.155502593.2416.1582128360856%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Is there a way to fork the jira-rest-java-client and pull in this fix: https://bitbucket.org/atlassian/jira-rest-java-client/pull-requests/93/jrjc-240-added-support-for-accountid/diff?_ga=2.137586672.1123302327.1582056915-228210608.1534538288 Atlassian has not merged that, but it looks like it solves the problem. 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.198679.155502593.2400.1582128300279%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues updated JENKINS-56987 Jenkins / JENKINS-56987 Atlassian Jira API Changes for GDPR Change By: Craig Rodrigues Resolution: Fixed Status: Fixed but Unreleased Reopened 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.198679.155502593.2392.1582128183160%40Atlassian.JIRA.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Craig Rodrigues assigned an issue to Radek Antoniuk Atlassian rolled out the change to JIRA Cloud for GDPR in the past few days, and this has completely broken the jira-plugin. See: https://community.atlassian.com/t5/Jira-questions/JIRA-REST-API-missing-parameters/qaq-p/1302944?utm_source=atlcomm_medium=email_campaign=kudos_comment_content=topic#U1305250 Jenkins / JENKINS-56987 Atlassian Jira API Changes for GDPR Change By: Craig Rodrigues Issue Type: Task Bug Assignee: Olivier Lamy Radek Antoniuk Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) --
[JIRA] (JENKINS-57239) Error while integrating jenkins and jira
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in plugin 3.0.12 Jenkins / JENKINS-57239 Error while integrating jenkins and jira Change By: Craig Rodrigues Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-39655) Adding JIRA plugin throws NullPointerException
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in plugin 3.0.12 Jenkins / JENKINS-39655 Adding JIRA plugin throws NullPointerException Change By: Craig Rodrigues Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title Craig Rodrigues resolved as Fixed Fixed in plugin 3.0.12 Jenkins / JENKINS-57695 Jira issue not created when jenkins build failed Change By: Craig Rodrigues Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-60305) Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required
Title: Message Title Craig Rodrigues commented on JENKINS-60305 Re: Jira plugin can't validate credentials due to breaking change in JIRA-- "permissions query parameter" is now required This seems to be fixed in JIRA Plugin 3.0.12 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.203300.1574868719000.1843.1582056720303%40Atlassian.JIRA.
[JIRA] (JENKINS-56474) agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8
Title: Message Title Renato Botelho commented on JENKINS-56474 Re: agent stuck in infinite loop at connect time on FreeBSD/arm with openjdk 8 I believe I saw the same issue here. Jenkins is running on a CentOS 7 box and I'm trying to configure a FreeBSD 13-CURRENT aarch64 as a builder node. Using the default openjdk package (version 8.232.09) I got the same problem. I decided then to go ahead and upgrade it to the latest version available on FreeBSD ports tree, which is 8.242.07.1. After that, it takes like 5 minutes to start, but after that it works. It throws these messages on console: <===[JENKINS REMOTING CAPACITY]===> channel started <===[JENKINS REMOTING CAPACITY]===> channel started Remoting version: 3.36.1This is a Unix agentFeb 12, 2020 11:40:39 AM hudson.remoting.UserRequest performWARNING: LinkageError while performing UserRequest:jenkins.slaves.StandardOutputSwapper$channelswap...@4c81d622java.lang.UnsatisfiedLinkError: Native library (com/sun/jna/freebsd-aarch64/libjnidispatch.so) not found in resource path ([]) at com.sun.jna.Native.loadNativeDispatchLibraryFromClasspath(Native.java:1032) at com.sun.jna.Native.loadNativeDispatchLibrary(Native.java:988) at com.sun.jna.Native.(Native.java:195) at hudson.util.jna.GNUCLibrary.(GNUCLibrary.java:115) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.swap(StandardOutputSwapper.java:60) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.call(StandardOutputSwapper.java:45) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.call(StandardOutputSwapper.java:39) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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) Agent successfully connected and online Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Craig Rodrigues commented on JENKINS-60925 Re: Integration with JIRA Radek Antoniuk I would ask for a few things in the docs: At https://plugins.jenkins.io/jira , update the screenshots with newer screenshots of the latest plugin. The latest plugin requires you to use a Jenkins Credential, instead of typing in a user and password Put the docs for JIRA Cloud closer to the top of https://plugins.jenkins.io/jira . It wasn't clear to me from reading that doc, that an API Token was required to log into JIRA via this plugin. 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.204322.158041457.1455.1580851080150%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head Devin Nusbaum If you have tested this a bit, can you merge this and deploy a new workflow-support-plugin? I keep hitting this at intermittent times, but I can never fully reproduce it. Unfortunately, this keeps hitting me right in the middle of when I am doing important stuff, and I don't have time to debug this. 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.196374.1545361815000.9094.1580425260909%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Craig Rodrigues commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command David Francecan you submit a PR of what you've got working to https://github.com/jenkinsci/jira-plugin ? 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.203639.1576745651000.8922.1580396220703%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Craig Rodrigues edited a comment on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command [~dfrance]can you submit a PR of what you've got working to https://github.com/jenkinsci/jira-plugin ? 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.203639.1576745651000.8924.1580396220833%40Atlassian.JIRA.
Re: Bounty for Intel AC9560 wireless support
On Thu, Nov 21, 2019 at 06:40:41AM +0800, Ben Woods wrote: > On Wed, 20 Nov 2019 at 11:42 pm, ma...@freebsd.org > wrote: > > > Hi Ben, > > > > Since I did that work under Foundation sponsorship I'd prefer to see > > the bounty donated to the FF. Please do include any notes you have > > about areas of FreeBSD that need improvement, especially related to > > missing laptop support. One pressing need is support for newer WiFi > > standards in iwm(4), and we're looking at that now. > > > Done! > > Evidence: https://pasteboard.co/IHCJyMY5.jpg > > Thanks again. > > #putyourmoneywhereyourmouthis > > Text from the donation: > > “ > Bounty for Intel AC9560 support - thank you! > https://lists.freebsd.org/pipermail/freebsd-wireless/2019-November/008921.html > > Idea: client to flash firmware updates from vendors: > https://fwupd.org/ > “ Nice, thanks Ben! ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: Bounty for Intel AC9560 wireless support
On Wed, Nov 20, 2019 at 06:42:54AM +0800, Ben Woods wrote: > Hi markj, > > It occurred to me that in mid October I replied to a post on Twitter > agreeing to chip in $100 for someone to spend the time to bring Intel > AC9560 support to FreeBSD: > https://twitter.com/woodsb02/status/1184599868381122561?s=21 > > Now that AC9560 support has been committed to head, I would like to ask how > I can send you $100. > > If there is not somewhere you can describe in this public forum, feel free > to privately reply to this email (dropping off the mailing list). > > Thanks again for the wireless driver - makes using my Thinkpad in FreeBSD > so much more enjoyable! Hi Ben, Since I did that work under Foundation sponsorship I'd prefer to see the bounty donated to the FF. Please do include any notes you have about areas of FreeBSD that need improvement, especially related to missing laptop support. One pressing need is support for newer WiFi standards in iwm(4), and we're looking at that now. ___ freebsd-wireless@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
WARNING : Your freebsd.org mailbox size exceeded quota : 5, 132 MB / 5.01 GB
___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
freebsd-net@freebsd.org is expiring in 3 days. Please confirm your email now.
___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
d...@freebsd.org is expiring in 3 days. Please confirm your email now.
___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Urgennt Security alert for your account freebsd-doc@freebsd.org from freebsd.org [Do not ignore]
___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Urgennt Security alert for your account d...@freebsd.org from freebsd.org [Do not ignore]
___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Email Account Verification
___ freebsd-doc@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred
Title: Message Title
Craig Rodrigues commented on JENKINS-52005
Re: catchError should give a visual hint in which stage the error occurred
I can reproduce this problem with this pipeline:
pipeline {
agent any
stages {
stage("Remove file which does not exist") {
steps {
catchError {
sh("rm /nonexistent")
}
}
}
stage("Hello!") {
steps {
sh("echo Hello1")
}
}
}
}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191506.1529326312000.22626.1557446880333%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred
Title: Message Title Craig Rodrigues updated an issue Jenkins / JENKINS-52005 catchError should give a visual hint in which stage the error occurred Change By: Craig Rodrigues Attachment: bad_nodes.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191506.1529326312000.22624.1557446880311%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52005) catchError should give a visual hint in which stage the error occurred
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-52005
Re: catchError should give a visual hint in which stage the error occurred
I can reproduce this problem with this pipeline:{noformat}pipeline {agent anystages {stage("Remove file which does not exist") {steps { catchError {sh("rm /nonexistent")}}}stage("Hello!") {steps {sh("echo Hello1")}}}}{noformat} !bad_nodes.png|thumbnail!The *Remove file which does not exist* node should be red, but it is green.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191506.1529326312000.22629.1557446940172%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head @Jason MCDev I talked to @abayer on the #jenkins IRC channel. He said that he thinks that this problem occurs if we rebuild a pipeline from a specific stage. During the build of a pipeline, an XML file is generated into the workspace which has flownode information. @abayer suggested a workaround of deleting the build from the build history to remove the flownode XML. Then the pipeline should be run from the beginning (not a rebuild). @abayer's suggestion doesn't match what I saw, since I did not rebuild from a stage, yet I saw 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.21341.1557356880308%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-55287
Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head
I encountered this:{noformat}Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[DEV/Porx-07/82:DEV/Porx-07 #82] but FlowNode was not found in storage for head id:FlowNodeId 1:121 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:664) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:901) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:912) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-55287
Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head
I encountered this: {noformat}Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[DEV/Porx-07/82:DEV/Porx-07 #82] but FlowNode was not found in storage for head id:FlowNodeId 1:121 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:664) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:901) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:912) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head I encountered this: Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[DEV/Porx-07/82:DEV/Porx-07 #82] but FlowNode was not found in storage for head id:FlowNodeId 1:121 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:664) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:901) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:912) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE Add Comment
[JIRA] (JENKINS-56998) Extended Choice plugin Wiki page incorrect
Title: Message Title Craig Rodrigues commented on JENKINS-56998 Re: Extended Choice plugin Wiki page incorrect Oleg Nenashev I withdrew my application to maintain this plugin. The current maintainer, @Vimil , monitors this e-mail: vimil.s...@gmail.com It looks like he doesn't monitor the other e-mails associated with his account, such as the one in his GitHub account. 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-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title Craig Rodrigues commented on JENKINS-56672 Re: Artifacts tab in blue ocean does not have link to view an artifact Patch submitted: https://github.com/jenkinsci/blueocean-plugin/pull/1951 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-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title Craig Rodrigues assigned an issue to Craig Rodrigues Jenkins / JENKINS-56672 Artifacts tab in blue ocean does not have link to view an artifact Change By: Craig Rodrigues Assignee: Craig Rodrigues 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-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title Craig Rodrigues started work on JENKINS-56672 Change By: Craig Rodrigues 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-39343) Persistent search/overviews/filtered views
Title: Message Title Craig Rodrigues commented on JENKINS-39343 Re: Persistent search/overviews/filtered views Reinhold Füreder I disagree. I work in a team where users (not just admins) need to get an overview of lots of jobs. The Blue Ocean overview is definitely not as good as the Classic UI for this. I'm facing this same issues as Sverre Moe. Those are all very good issues that you raise. If you haven't done so already, I recommend going to the https://gitter.im/jenkinsci/blueocean-plugin gitter channel and raise the issues you have there. It looks like Blue Ocean is not resourced as much as it was when the project was originally started, but there are are a few devs working on it, and they do monitor that channel. If you have time, you may also want to give it a try and try to understand the code and submit fixes I've started going that. 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-39343) Persistent search/overviews/filtered views
Title: Message Title Craig Rodrigues commented on JENKINS-39343 Re: Persistent search/overviews/filtered views I agree with @Sverre and others. The Blue Ocean UI for displaying hundreds of pipelines is worse than the Classic UI. If Blue Ocean had the ability to navigate through folders, that would be an improvement. Also, if Blue Ocean supported views, that would be an improvement. When you have hundreds of jobs, displaying everything in a flat namespace view, and requiring the user to search in order to filter the display of pipelines is not convenient. This gap in the UI/UX of Blue Ocean is one reason I constantly toggle back to the Classic UI. In the Classic UI, I make extensive use of folders and views to organize hundreds if Jenkins 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-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title Craig Rodrigues commented on JENKINS-56672 Re: Artifacts tab in blue ocean does not have link to view an artifact The behavior of the browser is determined by what the server sends back in the HTTP Content-Type field, and also the internal list of mime-types in the browser. If you appends */view/* to a URL, it triggers this behavior in Jenkins: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/DirectoryBrowserSupport.java#L308 It sets a pseudo-name to plain.txt, so that tricks the browser into trying to render the file in the browser. In my artifacts directory, I generate a lot of YAML files ending with .yml extension, so I want to be able to view them in the browser just like in the legacy UI, in addition to being able to download them. 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-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title Craig Rodrigues created an issue Jenkins / JENKINS-56672 Artifacts tab in blue ocean does not have link to view an artifact Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-03-22 00:49 Priority: Minor Reporter: Craig Rodrigues if I go to the Artifacts tab in blue ocean, I can see the artifacts. However, for each artifact I can only download the artifact. On the legacy UI, there was a link to view the artifact as well. For example https://myjenkins/jobname/29/artifact/somefile.txt will download the artifact https://myjenkins/jobname/29/artifact/somefile.txt/*view*/ will view it in the browser. I use that feature a lot because I archive certain log files during test runs which are handy to view in the browser. Add Comment
[JIRA] (JENKINS-34617) Make extended-choice-parameter-plugin pipeline compatibility easier
Title: Message Title Craig Rodrigues edited a comment on JENKINS-34617 Re: Make extended-choice-parameter-plugin pipeline compatibility easier I have a patch which allows you to specify ***extendedChoice* in the paramters parameters block of a declarative pipeline. [ https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/25 ] 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-34617) Make extended-choice-parameter-plugin pipeline compatibility easier
Title: Message Title Craig Rodrigues commented on JENKINS-34617 Re: Make extended-choice-parameter-plugin pipeline compatibility easier I have a patch which allows you to specify **extendedChoice in the paramters block of a declarative 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-34617) Make extended-choice-parameter-plugin pipeline compatibility easier
Title: Message Title Craig Rodrigues edited a comment on JENKINS-34617 Re: Make extended-choice-parameter-plugin pipeline compatibility easier I have a patch which allows you to specify ***extendedChoice* in the paramters block of a declarative pipeline. https://github.com/jenkinsci/extended-choice-parameter-plugin/pull/25 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-52825) Cannot see executors in Blue Ocean UI
Title: Message Title Craig Rodrigues updated JENKINS-52825 Fixed in https://github.com/jenkinsci/blueocean-plugin/pull/1909 Jenkins / JENKINS-52825 Cannot see executors in Blue Ocean UI Change By: Craig Rodrigues Status: In Progress Fixed but Unreleased Resolution: Fixed 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-52825) Cannot see executors in Blue Ocean UI
Title: Message Title Craig Rodrigues started work on JENKINS-52825 Change By: Craig Rodrigues 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.
