Re: Automatic website publishing

[David Blevins]

Thanks, David and Cesar!

The Jenkins part is working.  My tests runs that pushed to `asf-site` all 
worked and since the last email I've completed it and we now have automated 
publishing to the `asf-site` branch.  The job is setup to run daily, but any of 
us can click the 'Build Now' button at any time if you're impatient.

  - 
https://github.com/apache/tomee-site-pub/commit/3409970cd9cd0dbf806da49ff9edc0c37d152e46

FYI, Cesar, your test didn't work because you need to select `git-websites` as 
the node.  That has the credentials setup and permissions to publish to an 
`asf-site` or `asf-staging-*` branch.

What doesn't work is that our website was setup to use `master` not `asf-site`, 
so after the switch from `master` to `asf-site` updates do not reach 
https://tomee.apache.org.

I filed a ticket (INFRA-21903).  I worked a bit with @fluxo on #asfinfra and 
neither of us were able to figure it out.  I suspect @Humbedooh will get it 
resolved.

The good news is that when he does, we're completely setup for automated 
publishes to the website!

-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com

> On May 19, 2021, at 7:52 PM, Cesar Hernandez  wrote:
> 
> Hi David,
> 
> I tried to do these steps using jenkins pipeline with a test job here:
> https://ci-builds.apache.org/job/Tomee/job/test-pipeline/
> The problem [1] I'm getting seems to be related to the fact that the CI
> user doesn't have write access to the repo:
> 
> "remote: Permission to apache/tomee-site-pub.git denied to . "
> 
> 
> [1]
> 
> + git commit -m test publish from ci-builds.apache.org using jenkins
> [asf-staging-test 678b293a4] test publish from ci-builds.apache.org
> using jenkins
> 1 file changed, 1 insertion(+), 1 deletion(-)[Pipeline]
> withCredentials
> Masking
> supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD[Pipeline]
> { 
> [Pipeline]
> sh 
> 
> + git push origin HEAD:asf-staging-test
> remote: Permission to apache/tomee-site-pub.git denied to .
> fatal: unable to access 'https://github.com/apache/tomee-site-pub/':
> The requested URL returned error: 403[Pipeline] }[Pipeline] //
> withCredentials[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline]
> // node[Pipeline] End of PipelineERROR: script returned exit code 128
> Finished: FAILURE
> 
> 
> 
> 
> El mié, 19 may 2021 a las 19:03, David Blevins ()
> escribió:
> 
>> I've been trying to setup automatic website publishing.
>> 
>> So far I have a test Jenkins job that does a simple commit/push:
>> 
>> - https://ci-builds.apache.org/job/Tomee/job/site-publish
>> 
>> At the moment it's just a simple Freestyle job with a test script to see a
>> successful commit/push work:
>> 
>>git clone https://gitbox.apache.org/repos/asf/tomee-site-pub.git -b
>> asf-staging-test
>>cd tomee-site-pub
>>date > test.txt
>>git add test.txt
>>git commit -m "test publish from ci-builds.apache.org" test.txt
>>git push origin asf-staging-test
>> 
>> The trick and where I'm stuck is that we're using `master` as our main
>> branch for https://tomee.apache.org and Jenkins is setup to only let us
>> push a branch called `asf-site` or `asf-staging-*`
>> 
>> I've attempted to switch `tomee-site-pub` from `master` to `asf-site`, but
>> it doesn't seem to work.  I've filed a ticket with Infra and will keep you
>> updated:
>> 
>> - https://issues.apache.org/jira/browse/INFRA-21903
>> 
>> 
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>> 
>> 
> 
> -- 
> Atentamente:
> César Hernández.



smime.p7s
Description: S/MIME cryptographic signature

Re: Automatic website publishing

[Cesar Hernandez]

Hi David,

I tried to do these steps using jenkins pipeline with a test job here:
https://ci-builds.apache.org/job/Tomee/job/test-pipeline/
The problem [1] I'm getting seems to be related to the fact that the CI
user doesn't have write access to the repo:

"remote: Permission to apache/tomee-site-pub.git denied to . "


[1]

+ git commit -m test publish from ci-builds.apache.org using jenkins
[asf-staging-test 678b293a4] test publish from ci-builds.apache.org
using jenkins
 1 file changed, 1 insertion(+), 1 deletion(-)[Pipeline]
withCredentials
Masking
supported pattern matches of $GIT_USERNAME or $GIT_PASSWORD[Pipeline]
{ 
[Pipeline]
sh 

+ git push origin HEAD:asf-staging-test
remote: Permission to apache/tomee-site-pub.git denied to .
fatal: unable to access 'https://github.com/apache/tomee-site-pub/':
The requested URL returned error: 403[Pipeline] }[Pipeline] //
withCredentials[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline]
// node[Pipeline] End of PipelineERROR: script returned exit code 128
Finished: FAILURE




El mié, 19 may 2021 a las 19:03, David Blevins ()
escribió:

> I've been trying to setup automatic website publishing.
>
> So far I have a test Jenkins job that does a simple commit/push:
>
>  - https://ci-builds.apache.org/job/Tomee/job/site-publish
>
> At the moment it's just a simple Freestyle job with a test script to see a
> successful commit/push work:
>
> git clone https://gitbox.apache.org/repos/asf/tomee-site-pub.git -b
> asf-staging-test
> cd tomee-site-pub
> date > test.txt
> git add test.txt
> git commit -m "test publish from ci-builds.apache.org" test.txt
> git push origin asf-staging-test
>
> The trick and where I'm stuck is that we're using `master` as our main
> branch for https://tomee.apache.org and Jenkins is setup to only let us
> push a branch called `asf-site` or `asf-staging-*`
>
> I've attempted to switch `tomee-site-pub` from `master` to `asf-site`, but
> it doesn't seem to work.  I've filed a ticket with Infra and will keep you
> updated:
>
>  - https://issues.apache.org/jira/browse/INFRA-21903
>
>
> --
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
>
>

-- 
Atentamente:
César Hernández.

Re: Automatic website publishing

[David Jencks]

I got this working recently with the Aries website. I just ran ‘git branch 
asf-site’ and pushed and then my script worked. I run this from a Jenkins 
pipeline in the equivalent of tomee-site-generator ( if I remember the tomee 
repo name correctly).

There’s only one Aries pipeline so it should be easy to find if you want to 
take a look.

David jencks.

Sent from my iPhone

> On May 19, 2021, at 6:03 PM, David Blevins  wrote:
> 
> I've been trying to setup automatic website publishing.
> 
> So far I have a test Jenkins job that does a simple commit/push:
> 
> - https://ci-builds.apache.org/job/Tomee/job/site-publish
> 
> At the moment it's just a simple Freestyle job with a test script to see a 
> successful commit/push work:
> 
>git clone https://gitbox.apache.org/repos/asf/tomee-site-pub.git -b 
> asf-staging-test
>cd tomee-site-pub
>date > test.txt
>git add test.txt
>git commit -m "test publish from ci-builds.apache.org" test.txt
>git push origin asf-staging-test
> 
> The trick and where I'm stuck is that we're using `master` as our main branch 
> for https://tomee.apache.org and Jenkins is setup to only let us push a 
> branch called `asf-site` or `asf-staging-*`
> 
> I've attempted to switch `tomee-site-pub` from `master` to `asf-site`, but it 
> doesn't seem to work.  I've filed a ticket with Infra and will keep you 
> updated:
> 
> - https://issues.apache.org/jira/browse/INFRA-21903
> 
> 
> -- 
> David Blevins
> http://twitter.com/dblevins
> http://www.tomitribe.com
> 

Automatic website publishing

[David Blevins]

I've been trying to setup automatic website publishing.

So far I have a test Jenkins job that does a simple commit/push:

 - https://ci-builds.apache.org/job/Tomee/job/site-publish

At the moment it's just a simple Freestyle job with a test script to see a 
successful commit/push work:

git clone https://gitbox.apache.org/repos/asf/tomee-site-pub.git -b 
asf-staging-test
cd tomee-site-pub
date > test.txt
git add test.txt
git commit -m "test publish from ci-builds.apache.org" test.txt
git push origin asf-staging-test

The trick and where I'm stuck is that we're using `master` as our main branch 
for https://tomee.apache.org and Jenkins is setup to only let us push a branch 
called `asf-site` or `asf-staging-*`

I've attempted to switch `tomee-site-pub` from `master` to `asf-site`, but it 
doesn't seem to work.  I've filed a ticket with Infra and will keep you updated:

 - https://issues.apache.org/jira/browse/INFRA-21903


-- 
David Blevins
http://twitter.com/dblevins
http://www.tomitribe.com



smime.p7s
Description: S/MIME cryptographic signature

Re: Potential new home page

[Daniel Dias Dos Santos]

Hello,

I’m amazing the visual. congratulations to those involved :)



Em qua., 19 de mai. de 2021 às 16:18, Carlos Chacin 
escreveu:

> This looks great, thank you for all the efforts improving the website over
> the years to keep it even more relevant.
>
> Iterating over this sounds like the best approach.
>
> 
>
>
> On Wed, May 19, 2021, 12:10 PM David Blevins 
> wrote:
>
> > All,
> >
> > In celebration of our new accomplishment of being certified, I thought it
> > would be nice to have a refresh of the front page of the website to
> really
> > make people go "wow, there's some cool stuff happing over in TomEE."  I
> > enlisted the help of Ryan (designer) and Andrii (css/html/javascript) to
> > get something we can evaluate, then I setup a staging site using a branch
> > in the new tomee-site-pub repo.
> >
> >  - https://tomee-new-home-page.staged.apache.org/
> >
> > The revision is intentionally minimal.  The idea being to avoid a large
> > change and instead start very small and slowly iterate over time.
> >
> > So the primary question is do you think this is a good enough starting
> > point to publish and iterate upon over time?
> >
> > The Jakarta EE 9.1 release announcement is next Tuesday May 25th, so
> > ideally we can come up with something we're comfortable publishing by
> then.
> >
> >
> > -David
> >
> >
>

Re: Potential new home page

[Carlos Chacin]

This looks great, thank you for all the efforts improving the website over
the years to keep it even more relevant.

Iterating over this sounds like the best approach.




On Wed, May 19, 2021, 12:10 PM David Blevins 
wrote:

> All,
>
> In celebration of our new accomplishment of being certified, I thought it
> would be nice to have a refresh of the front page of the website to really
> make people go "wow, there's some cool stuff happing over in TomEE."  I
> enlisted the help of Ryan (designer) and Andrii (css/html/javascript) to
> get something we can evaluate, then I setup a staging site using a branch
> in the new tomee-site-pub repo.
>
>  - https://tomee-new-home-page.staged.apache.org/
>
> The revision is intentionally minimal.  The idea being to avoid a large
> change and instead start very small and slowly iterate over time.
>
> So the primary question is do you think this is a good enough starting
> point to publish and iterate upon over time?
>
> The Jakarta EE 9.1 release announcement is next Tuesday May 25th, so
> ideally we can come up with something we're comfortable publishing by then.
>
>
> -David
>
>

Potential new home page

[David Blevins]

All,

In celebration of our new accomplishment of being certified, I thought it would 
be nice to have a refresh of the front page of the website to really make 
people go "wow, there's some cool stuff happing over in TomEE."  I enlisted the 
help of Ryan (designer) and Andrii (css/html/javascript) to get something we 
can evaluate, then I setup a staging site using a branch in the new 
tomee-site-pub repo.

 - https://tomee-new-home-page.staged.apache.org/

The revision is intentionally minimal.  The idea being to avoid a large change 
and instead start very small and slowly iterate over time.

So the primary question is do you think this is a good enough starting point to 
publish and iterate upon over time?

The Jakarta EE 9.1 release announcement is next Tuesday May 25th, so ideally we 
can come up with something we're comfortable publishing by then.


-David



smime.p7s
Description: S/MIME cryptographic signature

Re: Converting "release-tools" from svn to git

[Jean-Louis Monteiro]

Thanks David - looks like good timing for upcoming 8.0.x maintenance
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Tue, May 18, 2021 at 7:17 PM David Blevins 
wrote:

> > On May 10, 2021, at 3:50 PM, David Blevins 
> wrote:
> >
> > We have some tools to help with release tasks in svn here:
> >
> > - http://svn.apache.org/repos/asf/tomee/sandbox/release-tools/
> >
> > I think I'm going to try to convert that over to git and put some love
> into them.  Not sure what runs and what doesn't.  I have to do the
> finishing steps for the 8.0.7 and 9.0.0-M7 so we'll see :)
>
> All converted.
>
>  - https://github.com/apache/tomee-release-tools
>
> A quick example of the commands currently there:
>
> ./target/release dist add-key
> ./target/release dist dev-to-release
> ./target/release dist list-releases
> ./target/release dist maven-to-dev
> ./target/release dist remove-release
> ./target/release release-notes generate
>
> The commands that are there are mostly around managing dist.apache.org
> and some initial code for generating the release notes.  Best case scenario
> is that over time we can get a handful of commands like this and the
> release process is that much easier to do and document.
>
>
> -David
>
>

Re: [DISCUSS] Release Apache TomEE 8.0.7 and 9.0.0-M7

[Jean-Louis Monteiro]

Great work David.
That's definitely good for visibility.
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, May 19, 2021 at 1:12 AM David Blevins 
wrote:

> > On May 18, 2021, at 10:31 AM, David Blevins 
> wrote:
> >
> > - Draft release notes for 9.0.0-M7 are available here:
> >   https://tomee.apache.org/9.0.0-M7/release-notes.html
> >
> > Remaining work:
> >
> > - Clean up "Dependency upgrade" section of release notes to reflect
> actual dependencies in the binary
>
> Ok!  I implemented it so any Dependency Upgrade JIRA marked as superseded
> is eliminated from the release notes.  This eliminates what we were seeing
> with 3 different versions of Tomcat listed and two different versions of
> MyFaces.  The new release notes are live:
>
>  - https://tomee.apache.org/9.0.0-M7/release-notes.html
>
> Sending out the "[ANN]" email shortly.
>
>
> -David
>
>