[JIRA] [seleniumhtmlreport] (JENKINS-18529) Feedback icons broken in Google Chrome
Jose Pedro Correia created JENKINS-18529 Feedback icons broken in Google Chrome Issue Type: Bug Assignee: m211 Attachments: Screenshot.png Components: seleniumhtmlreport Created: 27/Jun/13 1:23 PM Description: Cannot see feedback icons (green tick mark or red cross mark) in summary page on Google Chrome. Cannot see even see 'alt' text. See attached screenshot. The following post might be relevant for the 'alt' issue at least: http://stackoverflow.com/questions/5386570/how-to-display-alt-text-for-an-image-in-chrome Environment: Google Chrome version 27.0.1453.110 Project: Jenkins Priority: Major Reporter: Jose Pedro Correia 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] [seleniumhtmlreport] (JENKINS-18529) Feedback icons broken in Google Chrome
Jose Pedro Correia commented on JENKINS-18529 Feedback icons broken in Google Chrome Actually the icons are not visible in Firefox either on my machine. What could the problem be? In any case, in Firefox I get the 'alt' text at least, but in Google Chrome not even that is visible, as you see from the screenshot. Can that at least be 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 -- 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] [seleniumhtmlreport] (JENKINS-18529) Feedback icons broken in Google Chrome
Jose Pedro Correia commented on JENKINS-18529 Feedback icons broken in Google Chrome 404 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] [postbuildscript] (JENKINS-17389) Allow post build script actions to run before other post-build actions
Jose Pedro Correia commented on JENKINS-17389 Allow post build script actions to run before other post-build actions Well, the problem is exactly that the order of the post-build actions is not respected by this plugin. For example, say I have two post-build actions: archiving artifacts and a PostBuildScript action. Even if I put the PostBuildScript action BEFORE the artifact archival, when I run a build the PostBuildScript action is executed AFTER artifacts are archived. Plus it will move ITSELF to the end of the post-build actions. In my case this is important because my PostBuildScript action generates some artifacts that I want to archive, but currently this is impossible. P.S. - Why do you call this an old plugin if the last release was less than two months ago? Is there a more recent alternative? I've found the 'Post build task' plugin, but it is less powerful. 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-17389) Allow post build script actions to run before other post-build actions
Jose Pedro Correia created JENKINS-17389 Allow post build script actions to run before other post-build actions Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: postbuildscript Created: 27/Mar/13 3:58 PM Description: Currently, the PostBuildScript Plugin runs a set of actions only after all other post-build actions, even when it is placed before other post-build actions using the Jenkins UI. It would be very useful to be able to run actions before other post-build actions too. For example, I would like to run a script that produces artifacts that I would like to archive. This is currently impossible with this plugin, since the PostBuildScript actions necessarily run after the artifact archiving. Project: Jenkins Priority: Minor Reporter: Jose Pedro Correia 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-16132) More fine-grained conditioning of build outcome based on outcome of particular build steps
Jose Pedro Correia created JENKINS-16132 More fine-grained conditioning of build outcome based on outcome of particular build steps Issue Type: Improvement Assignee: Unassigned Components: core Created: 14/Dec/12 1:10 PM Description: I would like to be able to condition the outcome of a build for each build step, in a generic way (independently of the type of build step). What I mean is basically to generalize to any type of build step the three options provided by a parameterized trigger (https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Trigger+Plugin) build step when it is set to block (i.e. "Fail this build step if the triggered build is worse or equal to", "Mark this build as failure if the triggered build is worse or equal to" and "Mark this build as unstable if the triggered build is worse or equal to"). This would allow a more fine-grained control of the impact of each build step (e.g. "Don't fail/interrupt the build because this build step failed, but do mark the build as failure at the end..."). My use case: startup Tomcat with my application run some build steps (some ant targets, some shell build steps, etc) stop Tomcat do some more stuff The problem is I want to make sure the build step that stops Tomcat always runs if the startup ran, even if the steps in between failed. However, the build should be marked as failure in the end if those failed. Project: Jenkins Priority: Minor Reporter: Jose Pedro Correia 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-8871) Allow to use other SVN protocol than http/https
[ https://issues.jenkins-ci.org/browse/JENKINS-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160488#comment-160488 ] Jose Pedro Correia commented on JENKINS-8871: - Hi fcamblor, Thanks for the feedback (I just saw it now, sorry). I tried out that test job. It worked fine. However, I still have exactly the same problem... Allow to use other SVN protocol than http/https --- Key: JENKINS-8871 URL: https://issues.jenkins-ci.org/browse/JENKINS-8871 Project: Jenkins Issue Type: Improvement Components: scm-sync-configuration Reporter: fcamblor Assignee: fcamblor Attachments: scm-sync-configuration-0.0.5-bugfix8871-1.hpi Prior to v0.0.3, scm-sync-configuration plugin is relying on svnjava maven scm provider (see http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/ ), only http/https/file protocols are supported (for example svn+ssh is not supported). Eventually, a workaround would be to activate svnexe maven scm implementation for these case (Problem is : I don't know if we can have both svnexe svnjava plexus component activated in the same time) Nevertheless, the best point would be to have svnjava be compliant with every svn supported protocols. -- 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
[JIRA] (JENKINS-8871) Allow to use other SVN protocol than http/https
[
https://issues.jenkins-ci.org/browse/JENKINS-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159751#comment-159751
]
Pedro Correia commented on JENKINS-8871:
Hi everyone,
Don't know if anybody is still busy with this, but I was trying to get this
working.
Initially I ran into the same problem as reported by [~jchatham]:
{code}
Mar 2, 2012 1:41:15 PM hudson.plugins.scm_sync_configuration.SCMManipulator
checkout
SEVERE: [checkout] Error during checkout : SVN checkout failed.
Mar 2, 2012 1:41:15 PM hudson.plugins.scm_sync_configuration.SCMManipulator
scmConfigurationSettledUp
INFO: Creating scmRepository connection data ..
{code}
To try to fix this I manually checked out the
{{JENKINS_HOME/scm-sync-configuration/checkoutConfiguration}} directory. That
solves that problem, but now I get problems committing changes to the
configuration files:
{code}
Mar 2, 2012 1:48:13 PM hudson.plugins.scm_sync_configuration.SCMManipulator
checkinFiles
SEVERE: [checkinFiles] Problem during commit of [[config.xml]] : svn: Commit
failed (details follow):
svn: Authentication required for 'svn+ssh://tk7'
{code}
This is strange because I'm pretty sure the credentials are set up correctly...
Any thoughts?
Allow to use other SVN protocol than http/https
---
Key: JENKINS-8871
URL: https://issues.jenkins-ci.org/browse/JENKINS-8871
Project: Jenkins
Issue Type: Improvement
Components: scm-sync-configuration
Reporter: fcamblor
Assignee: fcamblor
Attachments: scm-sync-configuration-0.0.5-bugfix8871-1.hpi
Prior to v0.0.3, scm-sync-configuration plugin is relying on svnjava maven
scm provider (see
http://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/ ),
only http/https/file protocols are supported (for example svn+ssh is not
supported).
Eventually, a workaround would be to activate svnexe maven scm implementation
for these case (Problem is : I don't know if we can have both svnexe
svnjava plexus component activated in the same time)
Nevertheless, the best point would be to have svnjava be compliant with every
svn supported protocols.
--
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
