Sorry, my bad. This is not what I want to say.
I just want to note that it was very hard to find the solution for my
problem(s).
When I do a recap, it was probably better to read all the documentation
top down.
Don't get me wrong, I joined the community some years ago, because I
think jenkins
torial#Plugintutorial-SettingUpEnvironment
> as merely 'helpful', with parts 'probably unnecessary'? Without this file,
> it didn't work?
>
>> On 26.11.2016, at 09:17, Thomas Fürer <tfuerer.java...@gmail.com> wrote:
>>
>> finally i did it. v1.8.0 of thinBackup is ou
finally i did it. v1.8.0 of thinBackup is out now.
Well, thot took some doing.
What I've done:
* upgrade to parent pom 2.11 (-> look at thinBackup @ github)
* update the settings.xml temporary for this release and it looks like
this one
org.jenkins-ci.tools
jenkins
ly NOBODY has).
> You can fix this yourself. Read the README here:
> https://github.com/jenkins-infra/repository-permissions-updater/
>
> Cheers
> -Fritz
>
> On 06.11.2016 10:14, Thomas Fürer wrote:
>> Hi,
>>
>> I'm the maintainer of thinBackup-plugin and
o release thinBackup (actually NOBODY has).
> You can fix this yourself. Read the README here:
> https://github.com/jenkins-infra/repository-permissions-updater/
>
> Cheers
> -Fritz
>
> On 06.11.2016 10:14, Thomas Fürer wrote:
>> Hi,
>>
>> I'm the maintainer of
Hi,
I'm the maintainer of thinBackup-plugin and I want to release several
commits.
I tried it several time now with
mvn release:prepare release:perform -Dusername=tofuatjava -Dpassword=...
but I finally I get the error message
[INFO] [ERROR] Failed to execute goal
thank you Slide
Am 15.09.2016 um 18:00 schrieb Slide:
> I renamed thinBackup to thinbackup-plugin.
>
> On Thu, Sep 15, 2016 at 8:54 AM Thomas Fürer
> <tfuerer.java...@gmail.com <mailto:tfuerer.java...@gmail.com>> wrote:
>
> Hi Heiko,
>
> It's n
Hi Heiko,
It's not possible for me to fix this issue, because the Confluence
component adds automatically '-plugin' to the name but the component in
JIRA is still 'thinBackup'.
Maybe some admin could fix that...
Thomas
Weitergeleitete Nachricht
Betreff:thinBackup:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
+1
really cool
tom
Am 24.03.2016 um 07:02 schrieb R. Tyler Croy:
> I finished up the final work for migration from https://jenkins-ci.org
to
> https://jenkins.io today. The final step of the switchover was to redi
rect
> non-mapped URLs from
Hi,
I have done a release of my plugin thinbackup the other day. On github
it is marked as release as expected
(https://github.com/jenkinsci/thin-backup-plugin). but in the
updatecenter of jenkins it is not available. is there something I need
to change in the release process?
Thomas
--
You
you are my hero of the day,
godfather of permissions ;-)
thanks again,
thomas
Am 08.09.2015 um 05:05 schrieb Daniel Beck:
>
>> On 07.09.2015, at 08:53, Thomas Fürer <tfuerer.java...@gmail.com> wrote:
>>
>> Are you sure you add tofuatgit or tofuatjava to
'SCTMExecutor-plugin Developers'. Don't create new repos!
>
>> On 06.09.2015, at 12:47, Oleg Nenashev <o.v.nenas...@gmail.com> wrote:
>>
>> I have no permissions to check your permissions :(
>> CC'ed Daniel Beck, he should be able to do it.
>>
>> 2015-09-06 21:55
Hi Oleg,
thanks for helping, but why do I not have permissions to change
settings. I'm the founder, owner an maintainer of this plugin? I also
have a different plugin for jenkins (thinbackup) and here I'm able to
change the settings.
Regards,
Thomas
Am 06.09.2015 um 20:07 schrieb Oleg Nenashev:
Hi seb,
I'm wondering, because I'm not able to set ownership or commit rights on
this project, even I'm the maintainer and owner of this project.
So maybe one of the jenkins staff can help us.
Meanwhile I saw you allready forked the project, but I'm not sure if in
this case the release worflow
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I need to upgrade a 3rd party library to a version not provided by
jenkins core (commons-io 1.3 - 2.4). The problem is that sometimes I
get errors at runtime because the older commons-io is loaded. Some time
ago I red something about enforcing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry,
I found the documentation again
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Structure
Classloader
thanks,
Thomas
Am 13.04.2013 12:02, schrieb Thomas Fürer:
Hi,
I need to upgrade a 3rd party library to a version not provided
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi guys,
I know I can use google, and I have used it but I have different
problems and I do not know why it will work.
1) Running mvn release:prepare release:perform on windows
the buuild of the plugin is successfully, all tests are green (2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
jep would be fine to have one; have still some troubles with my plugin
if I have a high amount of data.
Am 13.12.2012 19:27, schrieb Stephen Connolly:
Can we get these renewed (add my name to the list)?
Anyone else needing them refreshed?
Hi there,
On 08/11/12 18:53, Thomas Fürer wrote:
Would someone by so kind and help me with moving my
plugins from svn to
github?
thinbackup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi admins,
Would someone by so kind and help me with moving my plugins from svn to
github?
thinbackup (https://svn.jenkins-ci.org/trunk/hudson/plugins/thinBackup/)
owner at github: tofuatgit, alienllama
silktestsuite
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Sebastian,
I found some old information
[quote]
This is the last major piece of the migration.
The subversion repository is being migrated to http://svn.jenkins-ci.org/
At this moment, it's synced with java.net and is read-only, but this
21 matches
Mail list logo