[JIRA] [core] (JENKINS-19760) Long hyperlinks in build description not displayed correctly on project page when using Markdown syntax
Sami Salonen
commented on JENKINS-19760
Long hyperlinks in build description not displayed correctly on project page when using Markdown syntax
This issue is about build descriptions only. I have not tested setting project descriptions. Build descriptions are visible on project page (Build History table) and naturally on the build page itself. Displaying build descriptions in Build History table (project page) seems to be the problem here.
Here is a sample shell script that sets the build description during the build.
jcli="ssh -p port jenkins host"
function get_first_link()
{
local text="first"
local url="" class="code-quote">"http://x.x.x.x/x/x/x/x?zzz=yyyaaa=bbbccc=dddeee=123"
# this does not work:
echo "[$text]($url)"
# this works:
# echo "a\ href="">$url\"$text/a"
}
function get_second_link()
{
this is similar to get_first_link
}
first=$( get_first_link )
second=$( get_second_link )
desc="$first\ $second"
$jcli set-build-description "$JOB_NAME" "$BUILD_NUMBER" "$desc"
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
Sami Salonen commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly The problem used to be permanent in my case. The good news is that I cannot reproduce it anymore. I tried to reproduce it in two different environments without luck: Env 1: Jenkins 1.509.4 + Email Extension 2.36 + Parameterized Trigger 2.22 Env 2: Jenkins 1.532.2 + Email Extension 2.37.2 + Parameterized Trigger 2.22 I cannot comment on the original problem regarding multi-configuration projects though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17503) Global exclude list of user accounts
Sami Salonen commented on JENKINS-17503 Global exclude list of user accounts Isn't it so that Email-ext gets the user IDs of committers? Could it then simply filter out blacklisted ones before requesting email address resolution for the remaining ones? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-12410) Downstream jobs not associated with upstream parent job properly
Sami Salonen commented on JENKINS-12410 Downstream jobs not associated with upstream parent job properly I have two free-style projects. The upstream project has a manual promotion process that triggers the downstream project. Jenkins default promotion action Build other projects works as expected whereas promotion actions Trigger/call builds on other projects and Trigger parameterized build on other projects by Parameterized Trigger plugin result in the following exception in the downstream project when trying to send an email to requesters. There is no additional info in jenkins log file, it just repeats the stack dump. Jenkins 1.480.3, Email-ext 2.28, Parameterized Trigger 2.17 Email was triggered for: Success Sending email for trigger: Success NOT overriding default server settings, using Mailer to create session messageContentType = text/html; charset=UTF-8 Adding recipients from recipient list Sending to requester ERROR: Could not send email as a part of the post-build publishers. java.lang.NullPointerException at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:537) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:304) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:296) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:256) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:718) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:693) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1546) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Some error occured trying to send the email...check the Jenkins log Finished: SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17503) Global exclude list of user accounts
Sami Salonen created JENKINS-17503 Global exclude list of user accounts Issue Type: New Feature Assignee: Alex Earl Components: email-ext Created: 06/Apr/13 8:24 PM Description: Our CI system uses so called build accounts to execute builds. These accounts are considered as committers as they do changes to vcs. These accounts do not have email addresses, or email addresses are invalid. Email addresses for committers are searched from directory server in our system. I would like to rule out these build accounts from email sending altogether. First implementation alternative is to have a global exclude list of user accounts. For these accounts, email address resolution would be skipped and thus the whole email sending. Second implementation alternative is to remove build account email addresses from the email message prior its sending. This is not as optimal as the first alternative as it requires email address resolution, but it gets the job done. This solution alternative requires configuration at global level too and is therefore related to JENKINS-14508. As a workaround, I can use project level pre-send script to filter out unwanted email addresses. Environment: Jenkins 1.480.3 Email-ext 2.28 Project: Jenkins Priority: Minor Reporter: Sami Salonen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16975) Artifacts is misspelled atrifacts in current groovy template groovy-html.template
Sami Salonen commented on JENKINS-16975 Artifacts is misspelled atrifacts in current groovy template groovy-html.template Looks like this was partially re-introduced while fixing JENKINS-16983. https://github.com/jenkinsci/email-ext-plugin/commit/c58234af501263c25729de7d0c6c48a7f7fe9ae9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-16975) Artifacts is misspelled atrifacts in current groovy template groovy-html.template
Sami Salonen reopened JENKINS-16975 Artifacts is misspelled atrifacts in current groovy template groovy-html.template Change By: Sami Salonen (06/Apr/13 8:39 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning Change By: Sami Salonen (17/Feb/13 12:06 PM) Component/s: ldap Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning
Sami Salonen commented on JENKINS-16844 Triggering a build from the context menu produces a warning Steps to reproduce: Start Jenkins (java -jar jenkins.war) Create a free-style project (default configuration is fine) Trigger a build from a context menu. Works fine. Add directory server based authentication: Click Enable security in global configuration From Access Control section, select LDAP under Security Realm Fill in Server, root DN, User search base, User search filter, Group search base, Manager DN, Manager Password (For Authorization, I tried both Anyone can do anything and Matrix-based security with same effect) Trigger a build from a context menu. Warning message is displayed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning Change By: Sami Salonen (17/Feb/13 12:23 PM) Environment: Jenkins1.480.3(WinstoneandTomcat) LDAPplugin1.1and1.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen
updated JENKINS-16844
Triggering a build from the context menu produces a warning when security is enabled
Change By:
Sami Salonen
(17/Feb/13 9:56 PM)
Summary:
Triggeringabuildfromthecontextmenuproducesawarning
whensecurityisenabled
Description:
Hoveringmouseoverajobnamebringsupacontextmenu.Clicking
BuildNow
_BuildNow_
fromthecontextmenuproducesthefollowingwarninganda
Proceed
_Proceed_
button.Buildstartsonlyif
Proceed
_Proceed_
buttonispressed.Contextmenuisaccessibleatleastinjoblistview(e.g.default
All
_All_
view)andfromthebreadcrumb.Clicking
BuildNow
_BuildNow_
ontheleftmenuonajobpageworksnormally
,i
.
e.withoutwarnings.
{{YoumustusePOSTmethodtotriggerbuilds.(Fromscriptsyoumayinsteadpassaper-projectauthenticationtoken,orauthenticatewithyourAPItoken.)Ifyouseethispage,itmaybebecauseapluginofferedaGETlink;fileabugreportforthatplugin.}}
Component/s:
core
Component/s:
security
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen edited a comment on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Steps to reproduce: Start Jenkins (java -jar jenkins.war) Create a free-style project (just give a name, default configuration is fine) Trigger a build from a context menu. Works fine. Add directory server based authentication: Click Enable security in global configuration From Access Control section, select LDAP under Security Realm Fill in Server, root DN, User search base, User search filter, Group search base, Manager DN, Manager Password (For Authorization, I tried both Anyone can do anything and Matrix-based security with same effect) Trigger a build from a context menu. Warning message is displayed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Sami Salonen updated JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Change By: Sami Salonen (18/Feb/13 7:27 AM) Component/s: gui This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning
Sami Salonen created JENKINS-16844 Triggering a build from the context menu produces a warning Issue Type: Bug Assignee: Unassigned Components: core Created: 16/Feb/13 9:55 PM Description: Hovering mouse over a job name brings up a context menu. Clicking Build Now from the context menu produces the following warning and a Proceed button. Build starts only if Proceed button is pressed. Context menu is accessible at least in job list view (e.g. default All view) and from the breadcrumb. Clicking Build Now on the left menu on a job page works normally. You must use POST method to trigger builds. (From scripts you may instead pass a per-project authentication token, or authenticate with your API token.) If you see this page, it may be because a plugin offered a GET link; file a bug report for that plugin. Environment: Jenkins 1.480.3 (Winstone and Tomcat) Project: Jenkins Priority: Major Reporter: Sami Salonen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google 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/groups/opt_out.
[JIRA] (JENKINS-12478) Free-style projects touch subversion authentication credentials file
Sami Salonen commented on JENKINS-12478 Free-style projects touch subversion authentication credentials file Issue is no longer reproducible with Jenkins 1.480.2 and Subversion plugin 1.45. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira --
[JIRA] (JENKINS-12478) Free-style projects touch subversion authentication credentials file
Sami Salonen closed JENKINS-12478 as Fixed Free-style projects touch subversion authentication credentials file Problem was present with Jenkins 1.480.2 and Subversion plugin 1.39 (comes with 1.480.2), but after plugin upgrade to 1.45 problem was gone. Change By: Sami Salonen (27/Jan/13 9:09 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-3681) Hide Empty Tabs (Views) in the GUI
[ https://issues.jenkins-ci.org/browse/JENKINS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163443#comment-163443 ] Sami Salonen commented on JENKINS-3681: --- This change introduces a small side effect. I use Sectioned View plugin to create a view, which does not contain projects, but informative content in textual format like FAQs, announcements, etc. With this change, this info view became unavailable for end users. As a workaround I added a List View section with one project to the bottom of the view. I also removed all columns from the section. This leaves two empty bars at the end of the view. It does not look pretty, but at least the view is visible to end users again. Jenkins version is 1.460. Hide Empty Tabs (Views) in the GUI -- Key: JENKINS-3681 URL: https://issues.jenkins-ci.org/browse/JENKINS-3681 Project: Jenkins Issue Type: Improvement Components: gui Affects Versions: current Environment: Platform: All, OS: All Reporter: rnell I'd like the ability to hide tabs that have no visible jobs. We use Project Based Security to limit development access to only their projects. I don't like that developers can still see all tabs used by the other groups, even though they are empty due to the security settings. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
