Re: GitHub link issue
On 25/08/15 15:42, Aaron Johnson wrote:
On this page
(https://wiki.jenkins-ci.org/display/JENKINS/NeoLoad+Plugin) there's a
link to GitHub that's incorrect. It's
https://github.com/jenkinsci/neoload-jenkins-plugin; but it should be
https://github.com/jenkinsci/neoload-plugin;
I can't see where to change this directly because the whole Plugin
Information section is generated by the line
{jenkins-plugin-info:pluginId=neoload-jenkins-plugin}. Anyone know
where I would go to update the link?
Plugin repositories are usually named like artifact-id-plugin, and
so that's what the infobox (generally) tries to link to by default.
But for plugins that have bad artifact IDs, the repository name can be
overridden via the sourceDir parameter. I've updated this wiki page
to include this.
Regards,
Chris
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/55DC73DC.6080307%40orr.me.uk.
For more options, visit https://groups.google.com/d/optout.
Re: Requesting hosting for plugin (Nouvola DiveCloud)
Any updates on this? Please let me know if any changes are needed before getting access, thanks! On Thursday, August 20, 2015 at 7:25:53 PM UTC-7, shawn.m...@nouvola.com wrote: Hi, I'm requesting hosting for a plugin. Here is the information: - The URL to your finished plugin repository on GitHub https://github.com/prossaro/Nouvola-DiveCloud-Jenkins-Plugin - The name the repository should have (if it doesn't already have a clear name), e.g. snapchat-notification-plugin nouvola-divecloud-plugin - Your personal GitHub username, if different from the username in the repo URL (GitHub organisation IDs are not supported) smacarth - Your jenkins-ci.org username, so we can make you the default assignee for the JIRA issue tracker component for your plugin smacarthur - A description of what the plugin does, and what makes it different from other similar plugins The plugin enables you to create a build step which will run a performance test on Nouvola DiveCloud (www.nouvola.com). DiveCloud lets you test your site or app with a specific load and geolocation, and provides insight into performance issues. - Thank you! Best, Shawn -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/16fc71df-3473-4392-9952-67be8ffb5645%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Commit Access JenkinsCI Github
That's also fine with me. The thing with testing is that the existing tests only cover the case of a freestyle job. The plugins functionality concerning matrix jobs is (so far) untested and it would have been quite an overhead to write those test for the minor changes I introduce. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/f73820c3-b01a-43c6-b168-39b40733a603%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hosting for New Plugin: jboss-deploy
Hi Daniel, I have tried to push changes to jboss-plugin repository but I can't access the repository for push: ERROR: Permission to jenkinsci/jboss-plugin.git denied to Daniel69. 2015-08-13 10:26 GMT-05:00 Daniel Beck m...@beckweb.net: Hi Daniel, Sorry about the delay! I made you a committer of the jboss-plugin. Please note that in general, we try to retain backwards compatibility with users' data if at all possible. Otherwise, plugin major versions are generally increased to indicate an incompatible change, and the new version declared incompatible with the old one. https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions You could also make use of the experimental update center before releasing any new version to existing users to solicit feedback. http://jenkins-ci.org/content/experimental-plugins-update-center Daniel On 30.07.2015, at 20:29, Daniel Bustamante Ospina dbustamant...@gmail.com wrote: Hi Daniel, Performing the merge can be a good idea, but the jboss-plugin is a bit outdated and it is based on a rather old version of jboss, nonetheless I could try to do it, but, could you give me commit access on this repository? 2015-07-30 10:06 GMT-05:00 Daniel Beck m...@beckweb.net: Hi Daniel, would it make sense to merge this and e.g. the jboss-plugin to provide comprehensive functionality in one place? On 27.07.2015, at 23:21, Daniel Bustamante Ospina dbustamant...@gmail.com wrote: Hi everyone, I've created a plugin for jboss deployment that I'd like to share with the Jenkins community. Repo: https://github.com/Daniel69/deploy-jboss-plugin Plugin name: deploy-jboss GitHub username: Daniel69 Jenkins username: dbustamante69 There are a couple of plugins that one could believe that are similar to this (deploy-plugin and jboss-plugin), but there is a big difference in the approach, this plugin is specially built for lastests mayor versions of JBoss and JBoss EAP (using jboss-as-controller-client) and supports deployments in domain mode as well as in standalone mode , which can not be achieved with the approach of neither mentioned plugins. ~Daniel. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ef3c0354-21e6-4a0e-befa-8195ee12fa91%40googlegroups.com . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/AxwuXVuRLyo/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CB6AED5F-5A7C-4CD9-81F6-E30CC16AD89C%40beckweb.net . For more options, visit https://groups.google.com/d/optout. -- -- Daniel Bustamante Ospina -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJNALEZK%3DQc2PAORz6_iVigMbiM-n1%2BfojQFcWVWsaP1saHbMA%40mail.gmail.com . For more options, visit https://groups.google.com/d/optout. -- -- Daniel Bustamante Ospina -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJNALEZ2%2Bzc0CWEjsqEBC8TEHpkEzp-Nt9tZALXxBuaZba1nCQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: ItemListener, onLocationChanged, modifying job property and saving. Result: after shutdown the modified property keeps the old value
Thank you, I've just seen today your answer, sorry.
It is working since 03-07-2015. It was a problem of misunderstood of the
Jenkins Inheritance plugin, and now it is working.
2015-07-05 10:41 GMT+02:00 Oleg Nenashev o.v.nenas...@gmail.com:
Did you try to launch the code in the debugger? If it reaches the save()
method, the project should be saved to XML file. You can check it contents
on the disk. If the data is available there, the issue may be related to
the loading procedure. More info is required to troubleshoot the issue w/o
having a code of your plugin.
пятница, 26 июня 2015 г., 17:54:23 UTC+3 пользователь Ramón Rial написал:
I want to be notified about Items changed locations, to modify some
properties of jobs with the new value.
I use the ItemListener:
@Extension
public class ItemOperations extends ItemListener {
public void onLocationChanged(Item item, String oldFullName, String
newFullName) {
System.out.println(ITEM location changed + oldFullName + +
newFullName + + item.getFullName());
if (!item instanceof InheritanceProject) {
return;
}
System.out.println(It is an InheritanceProject);
InheritanceProject inherited = (InheritanceProject) item;
InheritanceProject.clearBuffers(inherited);
//And then fixing all named references
for (InheritanceProject p : inherited.getProjectsMap().values()) {
for (AbstractProjectReference ref : p.getParentReferences()) {
System.out.println(ParentReference + ref.getName());
if (ref.getName().equals(oldFullName)) {
ref.switchProject(inherited);
}
}
for (AbstractProjectReference ref : p.compatibleProjects) {
System.out.println(compatibleProjects + ref.getName());
if (ref.getName().equals(oldFullName)) {
ref.switchProject(inherited);
}
}
try {
p.save();
} catch (Exception e) {
e.printStackTrace();
}
}
}
AbstractProjectReference is a property of the job, and I want change the
project which points to (it is a String property). After switching the
project (switchProject) all seems work right.
When I visit config page of the job I can see the new name, so it is OK.
Now I shutdown Jenkins, and I start it again.
I visit config page of the job again, but I see the old name, so it is
wrong.
Why the configuration of the job was not saved to disk?
P.D:
I have tried with:
try {
p.save();
} catch (Exception e) {
e.printStackTrace();
}
too, and the same result.
--
You received this message because you are subscribed to a topic in the
Google Groups Jenkins Developers group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/wB9m3BExwC8/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/50f288d7-2aef-4a74-9131-8d6e0de8404b%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-dev/50f288d7-2aef-4a74-9131-8d6e0de8404b%40googlegroups.com?utm_medium=emailutm_source=footer
.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/CAE0tYjdvaB%3DNMOXhiDgmp-rpb87t34K9tntPx25WzzdQhYiAdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Why is Jenkins using a HtmlUnit fork?
I think a README.md behind the code would be ok, since this project is used mainly by developers. On Tue, Aug 25, 2015 at 11:25 AM, Tom Fennelly tom.fenne...@gmail.com wrote: I eventually got rid of the forked version of HtmlUnit from Jenkins core in this PR https://github.com/jenkinsci/jenkins/pull/1774. Also see governance meeting notes on same https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Aug19meeting. This should result in us being able to use more modern JS libs in Jenkins + write tests against them that don't blow up in our face. Our forked version of HtmlUnit had inlined API extensions that no longer exist. I replaced all of these with static utility methods (in DomNodeUtil, HtmlFormUtil etc). I need to document these somewhere (also need to add more Javadoc as part of the PR). Where would be best? I could put a README.md in beside this code? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4a0b5562-107e-4c68-a253-98ff2d830e7f%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/4a0b5562-107e-4c68-a253-98ff2d830e7f%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Antonio Muñiz Software Engineer CloudBees, Inc. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQqhBv2oDwdr6qWSv59oZJHwvpt0AVHUzksg-cGhFui0A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Why is Jenkins using a HtmlUnit fork?
It would be great if someone could write up a small migration guide on the wiki for plugin devs that are upgrading their core dependency. Something like Where you used to do f.getButtonByCaption(Advanced...).click(); change to HtmlFormUtil.getButtonByCaption(f, Advanced...).click(); etc. On Tue, Aug 25, 2015 at 11:39 AM, Antonio Muñiz amu...@cloudbees.com wrote: I think a README.md behind the code would be ok, since this project is used mainly by developers. On Tue, Aug 25, 2015 at 11:25 AM, Tom Fennelly tom.fenne...@gmail.com wrote: I eventually got rid of the forked version of HtmlUnit from Jenkins core in this PR https://github.com/jenkinsci/jenkins/pull/1774. Also see governance meeting notes on same https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Aug19meeting. This should result in us being able to use more modern JS libs in Jenkins + write tests against them that don't blow up in our face. Our forked version of HtmlUnit had inlined API extensions that no longer exist. I replaced all of these with static utility methods (in DomNodeUtil, HtmlFormUtil etc). I need to document these somewhere (also need to add more Javadoc as part of the PR). Where would be best? I could put a README.md in beside this code? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4a0b5562-107e-4c68-a253-98ff2d830e7f%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/4a0b5562-107e-4c68-a253-98ff2d830e7f%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Antonio Muñiz Software Engineer CloudBees, Inc. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQqhBv2oDwdr6qWSv59oZJHwvpt0AVHUzksg-cGhFui0A%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQqhBv2oDwdr6qWSv59oZJHwvpt0AVHUzksg-cGhFui0A%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Robert Sandell *Software Engineer* *CloudBees Inc.* -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS21Y%2BW%3Dytwu%3Dzwj0mnx92j39-%2BQO%2B8XzO-CZETWuDqVZg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Why is Jenkins using a HtmlUnit fork?
I eventually got rid of the forked version of HtmlUnit from Jenkins core in this PR https://github.com/jenkinsci/jenkins/pull/1774. Also see governance meeting notes on same https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Aug19meeting. This should result in us being able to use more modern JS libs in Jenkins + write tests against them that don't blow up in our face. Our forked version of HtmlUnit had inlined API extensions that no longer exist. I replaced all of these with static utility methods (in DomNodeUtil, HtmlFormUtil etc). I need to document these somewhere (also need to add more Javadoc as part of the PR). Where would be best? I could put a README.md in beside this code? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4a0b5562-107e-4c68-a253-98ff2d830e7f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Plugin Hosting Request - Datadog Build Reporter
Thanks for the feedback! I agree, using credentials is better. I looked around to find a good way to grab the credentials list, and I am having a bit of trouble. Do you know of a good example of allowing the user to choose a credential from the `Manage Jenkins - Configure System` screen, and then retrieving that chosen credential again? On Monday, August 24, 2015 at 6:05:10 PM UTC-4, Kanstantsin Shautsou wrote: At first look https://github.com/DataDog/jenkins-datadog-plugin/blob/master/src/main/java/org/datadog/jenkins/plugins/datadogbuildreporter/DatadogBuildListener.java#L428 : - private String apiKey; - use credentials - stream handling probably requires tries - listener.getLogger().println(Started build!); - printing messages with unknown source place is a headache for debug, put some prefix ... -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e27747a4-05d6-4612-992e-6df6c66400d4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Plugin Hosting Request - Datadog Build Reporter
Better look on any existing plugin, you need 1) add credentials into plugin dependency 2) add in jelly/groovy page credentials form, then refer it as c:credentials… 3) add in descriptor magic doFill* method 4) store credentialsID instead direct apiKey 5) whenever you need real apiKey resolve credentialsId into real password and use it 6) don’t expose in jenkins API credentials for not auth people (have no examples). On Aug 26, 2015, at 01:07, John Zeller johnlzel...@gmail.com wrote: Thanks for the feedback! I agree, using credentials is better. I looked around to find a good way to grab the credentials list, and I am having a bit of trouble. Do you know of a good example of allowing the user to choose a credential from the `Manage Jenkins - Configure System` screen, and then retrieving that chosen credential again? On Monday, August 24, 2015 at 6:05:10 PM UTC-4, Kanstantsin Shautsou wrote: At first look https://github.com/DataDog/jenkins-datadog-plugin/blob/master/src/main/java/org/datadog/jenkins/plugins/datadogbuildreporter/DatadogBuildListener.java#L428 https://github.com/DataDog/jenkins-datadog-plugin/blob/master/src/main/java/org/datadog/jenkins/plugins/datadogbuildreporter/DatadogBuildListener.java#L428 : - private String apiKey; - use credentials - stream handling probably requires tries - listener.getLogger().println(Started build!); - printing messages with unknown source place is a headache for debug, put some prefix ... -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/GXkpWaPm-wE/unsubscribe https://groups.google.com/d/topic/jenkinsci-dev/GXkpWaPm-wE/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscr...@googlegroups.com mailto:jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/e27747a4-05d6-4612-992e-6df6c66400d4%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/e27747a4-05d6-4612-992e-6df6c66400d4%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/D73C7672-5720-483C-8B43-FD5730C4D69B%40gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Next Windows Slave Installer release
The module has not been released yet. I think it makes sense to bump the winsw dependency to 1.18 in order to get several bugfixes. вторник, 25 августа 2015 г., 15:26:17 UTC+3 пользователь Claus Schneider написал: Hi guys A follow-up on the JUES.. Great event and integrated code.. :) The https://github.com/jenkinsci/windows-slave-installer-module/pull/2 https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fjenkinsci%2Fwindows-slave-installer-module%2Fpull%2F2sa=Dsntz=1usg=AFQjCNEzpoDh7mvkTMwhWks19mE0HSALgQ is merged in to the repo. I have tried to install the lastest weekly (1.626 ), but it seems the change is not included. Kohsuke mentioned that it should be automatically in the upcoming weekly. Unfortunately so far I have not found any indication on the Change Log nor does it seem the change is included.. Or did it have a problem? Can I have an estimate of the release? Thanks a lot in advance.. // Claus Schneider -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/21d10121-5338-4d1b-b6f3-b65b69aba611%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Plugin Hosting Request - drupal
Could you explain a use case of the plugin? Is it designed for the Drupal core development only or for the easy Drupal plugins CI? понедельник, 24 августа 2015 г., 20:22:52 UTC+3 пользователь Fengtan написал: Plugin Repo: https://github.com/fengtan/drupal-plugin Plugin Name: drupal-plugin Jenkins-Ci.org User: fengtan Description: A plugin to review code https://www.drupal.org/project/coder and run tests https://www.drupal.org/simpletest on Drupal https://www.drupal.org/. Results can be published using Checkstyle https://wiki.jenkins-ci.org/display/JENKINS/Checkstyle+Plugin and JUnit https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Plugin. It is already possible to do this using a Shell builder https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project#Buildingasoftwareproject-ShellScriptsandWindowsBatchCommands and/or the Phing Drush Task https://github.com/kasperg/phing-drush-task. What this plugin provides is a user-friendly interface to configure things in a few clicks right in the Jenkins interface. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2f12e75e-34b9-4e7d-a4d8-4f5484aa12d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: install CD (Was RE: Revisiting bundled plugins)
Currently there is no ISO images. ISO image could be packed, but what do you expect to see there? I doubt there are much advantages for a clean Jenkins there. Jenkins + a set of plugins could be packed in such way using Juseppe http://jenkins-ci.org/content/juseppe-custom-update-site-jenkins or other such things. It also needs a customized installer for each platform. It could be done, but the required efforts are quite big. понедельник, 24 августа 2015 г., 19:54:22 UTC+3 пользователь Jan Ruzicka написал: Hi Is there such option as to have Installation ISO image with the Update center? This would be nice for places that have to work offline. Jan -Original Message- From: jenkin...@googlegroups.com javascript: [mailto: jenkin...@googlegroups.com javascript:] On Behalf Of Jesse Glick Sent: Monday, August 24, 2015 11:41 AM To: Jenkins Dev jenkin...@googlegroups.com javascript: Subject: Re: Revisiting bundled plugins On Sun, Aug 23, 2015 at 2:47 PM, Sacha Labourey sa...@cloudbees.com javascript: wrote: This setup makes the (high) availability (and bandwidth capacity) of the update center (the setup center in that scenario) a key requirement (center down = no install of Jenkins is possible anymore). http://updates.jenkins-ci.org/ is already mirrored and the servers are expecting heavy traffic. And with the _current_ WAR you already need to hit the UC just to get, say, Git support. So I do not think this is a reason to bloat the standard download. It is always possible to produce an ISO image of Jenkins with the top 200 plugins preinstalled for overnight mailing of CDs to benighted regions of the world, such as central Massachusetts. :-) Also I agree with Daniel that we should not “check by default” traditionally bundled plugins without a good reason, i.e., other than compatibility for upgrades of split plugins. How many people really use `external-monitor-job`, or even know what it does? This is just a feature that Kohsuke at some point (years ago) decided would be neat to implement, and happened to put in core. Certainly does not have as broad appeal as, say, `matrix-project` (currently bundled), or `cloudbees-folder` (currently not). Yet it clutters everyone’s _New Item_ screen with a mysterious option. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1hk2F1jG2N5r921UgnUB3XtfaqG-j58%2BYFEu53vMGcYA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. NOTICE TO RECIPIENT: This email, including attachments, may contain information which is confidential, proprietary, attorney-client privileged and/or controlled under U.S. export laws and regulations and may be restricted from disclosure by applicable State and Federal law. Nothing in this email shall create any legal binding agreement between the parties unless expressly stated herein and provided by an authorized representative of Comtech Telecommunications Corp. or its subsidiaries. If you are not the intended recipient of this message, be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify us immediately by return email and permanently delete all copies of the original email and any attached documentation from any computer or other media. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5c0f92c8-ff46-4af1-92b8-38d3fa427af0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Why is Jenkins using a HtmlUnit fork?
Absolutely, this is the sort of documentation I'm planning to add. On Tuesday, August 25, 2015 at 10:51:08 AM UTC+1, Robert Sandell wrote: It would be great if someone could write up a small migration guide on the wiki for plugin devs that are upgrading their core dependency. Something like Where you used to do f.getButtonByCaption(Advanced...).click(); change to HtmlFormUtil.getButtonByCaption(f, Advanced...).click(); etc. On Tue, Aug 25, 2015 at 11:39 AM, Antonio Muñiz amu...@cloudbees.com javascript: wrote: I think a README.md behind the code would be ok, since this project is used mainly by developers. On Tue, Aug 25, 2015 at 11:25 AM, Tom Fennelly tom.fe...@gmail.com javascript: wrote: I eventually got rid of the forked version of HtmlUnit from Jenkins core in this PR https://github.com/jenkinsci/jenkins/pull/1774. Also see governance meeting notes on same https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Aug19meeting. This should result in us being able to use more modern JS libs in Jenkins + write tests against them that don't blow up in our face. Our forked version of HtmlUnit had inlined API extensions that no longer exist. I replaced all of these with static utility methods (in DomNodeUtil, HtmlFormUtil etc). I need to document these somewhere (also need to add more Javadoc as part of the PR). Where would be best? I could put a README.md in beside this code? -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4a0b5562-107e-4c68-a253-98ff2d830e7f%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-dev/4a0b5562-107e-4c68-a253-98ff2d830e7f%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Antonio Muñiz Software Engineer CloudBees, Inc. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQqhBv2oDwdr6qWSv59oZJHwvpt0AVHUzksg-cGhFui0A%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzQqhBv2oDwdr6qWSv59oZJHwvpt0AVHUzksg-cGhFui0A%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- Robert Sandell *Software Engineer* *CloudBees Inc.* -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c1a7455e-4b21-493d-bb6b-fd1406a0c6c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Hosting for New Plugin: jboss-deploy
Check your inbox for an invitation from GitHub. On 25.08.2015, at 21:01, Daniel Bustamante Ospina dbustamant...@gmail.com wrote: Hi Daniel, I have tried to push changes to jboss-plugin repository but I can't access the repository for push: ERROR: Permission to jenkinsci/jboss-plugin.git denied to Daniel69. 2015-08-13 10:26 GMT-05:00 Daniel Beck m...@beckweb.net: Hi Daniel, Sorry about the delay! I made you a committer of the jboss-plugin. Please note that in general, we try to retain backwards compatibility with users' data if at all possible. Otherwise, plugin major versions are generally increased to indicate an incompatible change, and the new version declared incompatible with the old one. https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions You could also make use of the experimental update center before releasing any new version to existing users to solicit feedback. http://jenkins-ci.org/content/experimental-plugins-update-center Daniel On 30.07.2015, at 20:29, Daniel Bustamante Ospina dbustamant...@gmail.com wrote: Hi Daniel, Performing the merge can be a good idea, but the jboss-plugin is a bit outdated and it is based on a rather old version of jboss, nonetheless I could try to do it, but, could you give me commit access on this repository? 2015-07-30 10:06 GMT-05:00 Daniel Beck m...@beckweb.net: Hi Daniel, would it make sense to merge this and e.g. the jboss-plugin to provide comprehensive functionality in one place? On 27.07.2015, at 23:21, Daniel Bustamante Ospina dbustamant...@gmail.com wrote: Hi everyone, I've created a plugin for jboss deployment that I'd like to share with the Jenkins community. Repo: https://github.com/Daniel69/deploy-jboss-plugin Plugin name: deploy-jboss GitHub username: Daniel69 Jenkins username: dbustamante69 There are a couple of plugins that one could believe that are similar to this (deploy-plugin and jboss-plugin), but there is a big difference in the approach, this plugin is specially built for lastests mayor versions of JBoss and JBoss EAP (using jboss-as-controller-client) and supports deployments in domain mode as well as in standalone mode , which can not be achieved with the approach of neither mentioned plugins. ~Daniel. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/ef3c0354-21e6-4a0e-befa-8195ee12fa91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Developers group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/AxwuXVuRLyo/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CB6AED5F-5A7C-4CD9-81F6-E30CC16AD89C%40beckweb.net. For more options, visit https://groups.google.com/d/optout. -- -- Daniel Bustamante Ospina -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAJNALEZK%3DQc2PAORz6_iVigMbiM-n1%2BfojQFcWVWsaP1saHbMA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. -- -- Daniel Bustamante Ospina -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/18B44EF9-7FCC-4A0A-A410-31F582FB86B5%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Re: Plugin image in job's Jelly config
Please provide a link to the plugin or to the piece of code, where you suffer from the image resolution issue. img tag should work everywhere IIRC понедельник, 24 августа 2015 г., 17:41:42 UTC+3 пользователь Kirill написал: Hi all, Is it possible to show an image from a particular plugin on job's configuration page? I looked at https://jenkins-ci.org/maven-site/jenkins-core/jelly-taglib-ref.html, but there doesn't seem to be a Jelly tag for this. I tried to use smth like img src=/plugin/my-plugin/24x24/warning.png/ - but it doesn't get resolved. The same location, btw, works fine when used on build's summary page. -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/96135480-4ec4-4bf0-bd44-7917f556f821%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Pull request on junit-plugin - Permission to release
Hi, I just opened a pull request to the junit-plugin to export some extra information via the REST Api: https://github.com/jenkinsci/junit-plugin/pull/25 Would it be OK for the maintainers if I merge it and pull a new release? Since the change is only an Annotation I suppose there should not be any problems. Best regards, Stefan -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/103661b7-7fc2-470f-a96d-c32f1a0e4733%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Next Windows Slave Installer release
Hi guys A follow-up on the JUES.. Great event and integrated code.. :) The https://github.com/jenkinsci/windows-slave-installer-module/pull/2 https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fjenkinsci%2Fwindows-slave-installer-module%2Fpull%2F2sa=Dsntz=1usg=AFQjCNEzpoDh7mvkTMwhWks19mE0HSALgQ is merged in to the repo. I have tried to install the lastest weekly (1.626 ), but it seems the change is not included. Kohsuke mentioned that it should be automatically in the upcoming weekly. Unfortunately so far I have not found any indication on the Change Log nor does it seem the change is included.. Or did it have a problem? Can I have an estimate of the release? Thanks a lot in advance.. // Claus Schneider -- You received this message because you are subscribed to the Google Groups Jenkins Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/98e8b50e-81e0-44fd-a818-8d92e07c627d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
GitHub link issue
Hello,
On this page (https://wiki.jenkins-ci.org/display/JENKINS/NeoLoad+Plugin)
there's a link to GitHub that's incorrect. It's
https://github.com/jenkinsci/neoload-jenkins-plugin; but it should be
https://github.com/jenkinsci/neoload-plugin;
I can't see where to change this directly because the whole Plugin
Information section is generated by the line
{jenkins-plugin-info:pluginId=neoload-jenkins-plugin}. Anyone know where
I would go to update the link?
thanks
-Aaron
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/3f874aaf-e6e7-4db9-b568-60776fefcc9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
