I am a new baby to Jenkins and I could not go all the old posts to look for
what I need help !
I have a Jenkins setup and my Jenkins monitors a specific file such as the
lastbuildfound.txt in builds folder. This text file contains the last
successful build no.
Whenever this text file is
On 25 March 2015 at 07:49, Nigel Magnay nigel.mag...@gmail.com wrote:
I think there's confusion over 'support' and 'develop'. Going JDK8 should
not imply dropping non-JDK6 versions:
Take Tomcat as an example. Tomcat 9 requires a newer JDK than Tomcat 8.
That does not mean that Tomcat 8 isn't
I think there's confusion over 'support' and 'develop'. Going JDK8 should
not imply dropping non-JDK6 versions:
Take Tomcat as an example. Tomcat 9 requires a newer JDK than Tomcat 8.
That does not mean that Tomcat 8 isn't receiving 'support', or that it's
stopped working - it's getting fixes,
I have added checkRoles within my FileCallable implementation, but it still
fails. Though this time with a different message.
remote file operation failed: /home/build/jenkins/workspace/myMatrixProject at
hudson.remoting.Channel@54e95cec:Development-opensuse-x86_64:
java.io.IOException: Unable
JDK7 is end of life after April 2015, so in May 2015 if we pick the second
model then we would be JDK8 but the LTS released in late April will
have been JDK7 and JDK8... as technically only at then end of April is JDK7
EOL.
The advantage of the second model is that the July LTS will
Hi all,
In the plugin I'm currently writing, I reference promoted-builds(-plugin)
v2.20. I'm pretty satisfied with this version of the plugin.
On the test environment I decided to add also
parametrized-trigger(-plugin). Which depends on promoted-builds(-plugin)
v2.10.
During the execution of my
Dear Team,
vncviewer plugin lets you start JavaScript based VNC viewer via HTML link
directly from 'Console output' of the job.
Subversion path pf plugin:
https://svn.jenkins-ci.org/trunk/hudson/plugins/vncviewer
Regards
Dimitri Tenenbaum
--
You received this message because you are
I agree with Daniel and Oleg, I also think it is misleading - maybe not to he
ones how know this tool - but to everyone else and I would say thats about 90%
..my 2cents
/Domi
On 25 Mar 2015, at 14:42, advinst caphyon advinst.caph...@gmail.com wrote:
Hi,
Advanced Installer is a recognized
Hi,
Here is the plugin repo:
https://github.com/advinst/advinst-jenkins-plugin
Any update o this?
Thanks.
On Tuesday, March 24, 2015 at 8:48:57 AM UTC+2, Oleg Nenashev wrote:
As I see, the plugin does not exist in your repo.
Could you clarify the purpose of the plugin (e.g. describe the
Hi,
Advanced Installer is a recognized name in the packaging solutions market.
The id will not be misleading to our users which requested this plugin.
Also we would like to use the same naming scheme as similar products (wix,
InstallShield).
So if it is not inconvenient we would like to keep
Dear group,
i followed the instructions layed out
in
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues.
Am i still on track?
Thanks
Jochen
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers
• Is this something for the governance board to decide at the next
meeting?
Next meeting's agenda is already more than full.
People have their opinions but we need to move forward to reach a decision of
which there is not one solution that meets everyone's requirements.
We should
Do you consider changing the artifactId?
The current one is quite confusing. I think that Daniel's proposal could be
a right choice for your plugin
2015-03-25 16:01 GMT+03:00 advinst caphyon advinst.caph...@gmail.com:
Hi,
Here is the plugin repo:
On Wed, Mar 25, 2015 at 5:31 AM, Ivo Bellin Salarin
ivo.bellinsala...@gmail.com wrote:
I suppose this is related to the version of the plugin.
Perhaps.
Is there a way to control the (version of the) class being used? Is this due
to a change in
the interface of the called class?
No, you can
I must admit that the parametrized trigger is not a dependency of my
plugin. I've copied it in the plugins folder of my dev environment because
it is present in our production environment.
Fearing a similar crash in the production environment, I preferred ask the
question to confirmed
On Wed, Mar 25, 2015 at 6:53 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Which is why I think going for JDK7 now is a better plan than trying to jump
all the way to JDK8
Painful as it is, I tend to agree. To be clear, by current LTS policy,
switching the baseline to Java 8 means
Thanks so much.
Il giorno mer 25 mar 2015 17:47 Jesse Glick jgl...@cloudbees.com ha
scritto:
On Wed, Mar 25, 2015 at 12:38 PM, Ivo Bellin Salarin
ivo.bellinsala...@gmail.com wrote:
I must admit that the parametrized trigger is not a dependency of my
plugin.
I've copied it in the plugins
On Wed, Mar 25, 2015 at 7:55 AM, nicolas de loof
nicolas.del...@gmail.com wrote:
new programmation options, not just new filesystem API (that we use via
XMLFile anyway)
To be clear, there is code scattered all over Jenkins core (and some
plugins) which would benefit significantly from
On Wed, Mar 25, 2015 at 12:38 PM, Ivo Bellin Salarin
ivo.bellinsala...@gmail.com wrote:
I must admit that the parametrized trigger is not a dependency of my plugin.
I've copied it in the plugins folder of my dev environment because it is
present in our production environment.
If you feel there
Very nice, Just what I need!
+1
2015-03-25 6:54 GMT-03:00 Dimitri Tenenbaum dim.tb...@gmail.com:
Dear Team,
vncviewer plugin lets you start JavaScript based VNC viewer via HTML link
directly from 'Console output' of the job.
Subversion path pf plugin:
f:radioBlock is not hiding child object by default. I have to select
another radio in the same group to make the items hidden.
f:entry field=method
f:section title=Deployment method
f:entry
I didn't mean to kick up this much of a shit storm!
People have their opinions but we need to move forward to reach a decision
of which there is not one solution that meets everyone's requirements.
What is the next steps here?
- Do we vote on the following options:
1. Support the
The underlying question is indeed to determine project rules considering
supported runtime
1. Support the current and previous verions of the Oracle JDK
2. Support the JDKs that Oracle support
3. do nothing and stick with Java6 until 2020.
We already decide to move from 1.5 to 6, and
On 25 March 2015 at 09:20, Nigel Magnay nigel.mag...@gmail.com wrote:
JDK7 is end of life after April 2015, so in May 2015 if we pick the
second model then we would be JDK8 but the LTS released in late April
will have been JDK7 and JDK8... as technically only at then end of April is
Tried the following that got rid of Unable to serialize, but still does
not work. Most of the examples I find online for FilePath.act does not work
in Script Console.
import hudson.FilePath.FileCallable
import hudson.remoting.VirtualChannel
import org.jenkinsci.remoting.RoleChecker
def
Dear Jenkins
Here is the needed info to host a plugin
- your GitHub plugin name: *almasw-modbuilder-plugin*
- your personal GitHub ID: *atejeda*
- The existing GitHub repository to fork:
*https://github.com/atejeda/almasw-modbuilder-plugin.git*
thanks in advance.
--
You received
26 matches
Mail list logo
