You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Shawn McKinney <sm...@apache.org> on 2021/07/11 13:33:04 UTC

[RESULT] [VOTE] Apache Fortress 2.0.6 release (take 2)

Closing with 3 binding votes, Stefan, Emmanuel and my +1.

Thanks

—
Shawn

> On Jul 11, 2021, at 4:15 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
> 
> +1
> 
> Checked the licenses.
> Checked the signatures and checksums.
> Built all 4 projects with Java 11.
> Run the Apache Fortress Core Integration Test against OpenLDAP.
> 
> Kind Regards,
> Stefan
> 
> On 7/11/21 5:49 AM, Emmanuel Lécharny wrote:
>> Checked the release,
>> checked the signaturre,
>> 
>> +1 from me !
>> 
>> On 08/07/2021 20:56, Stefan Seelmann wrote:
>>> FYI, I won't have time before Sunday to check the release.
>>> 
>>> On 7/6/21 8:57 PM, Shawn McKinney wrote:
>>>> I have removed (and verified) the jboss jar dependency from fortress
>>>> rest.  The repos are retagged. Artifacts rebuilt and staged once
>>>> again. Let’s try this again...
>>>> 
>>>> 
>>>> Hello,
>>>> 
>>>> This is an announcement to vote for the next release of Apache
>>>> Directory Fortress, 2.0.6.
>>>> 
>>>> Here are the list of bugs and enhancements:
>>>> 
>>>> https://issues.apache.org/jira/projects/FC/versions/12349361
>>>> 
>>>> A tag created for git: ‘2.0.6', and the sources may be pulled using
>>>> git commands:
>>>> git clone --branch 2.0.6
>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
>>>> git clone --branch 2.0.6
>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
>>>> git clone --branch 2.0.6
>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git
>>>> git clone --branch 2.0.6
>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
>>>>     
>>>> with their associated checksums:
>>>> - core:  33ac2682170e26272cdc05b370f6c1ffcd834edc
>>>> - realm: f4777d0842e4a93ad35b4f2ed3d00d9d185728ed
>>>> - rest:  35a96e40030182a99a4c8cd9effad5ddc0b4bc45
>>>> - web:   647356f53fcc9406d434fee8a0d13123dbcde510
>>>> 
>>>> Or, source and binary distros may be downloaded from SVN:
>>>> - https://dist.apache.org/repos/dist/dev/directory/fortress/2.0.6/
>>>> 
>>>> The staging repo on Nexus:
>>>> -
>>>> https://repository.apache.org/content/repositories/orgapachedirectory-1203
>>>> 
>>>> 
>>>> Test against LDAP using one of these:
>>>> -
>>>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-APACHEDS.md
>>>> 
>>>> -
>>>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-SLAPD.md
>>>> 
>>>> 
>>>> - Choose one of the above.  Complete (only) the sections leading up
>>>> to and including the SECTION entitled: 'Apache Fortress Core
>>>> Integration Test’
>>>> 
>>>> Please vote:
>>>> [ ] +1   | Release Fortress 2.0.6
>>>> [ ] +/-0 | Abstain
>>>> [ ] -1   | Do *NOT* Release Fortress 2.0.6
>>>> 
>>>> 
>>>> —
>>>> Shawn
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
>>>> For additional commands, e-mail: dev-help@directory.apache.org
>>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
>>> For additional commands, e-mail: dev-help@directory.apache.org
>>> 
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
> For additional commands, e-mail: dev-help@directory.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
For additional commands, e-mail: dev-help@directory.apache.org


Re: [RESULT] [VOTE] Apache Fortress 2.0.6 release (take 2)

Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 15, 2021, at 8:43 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
> 
> N&L checks would mainly be checking that the packages contain them.
> 
>> And, what should it be written in — Bash?
> 
> Yes, or whatever works.

My choice is clearly ansible.  There’s already a playbook written that does everything leading up to (and including) the integration tests.  It’s what I use.  Would just need to add something to do the file checks.

Ansible is more robust than just bash and handles the intricacies of platform better IMO.

—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org


Re: [RESULT] [VOTE] Apache Fortress 2.0.6 release (take 2)

Posted by Emmanuel Lécharny <el...@gmail.com>.

On 15/07/2021 15:30, Shawn McKinney wrote:
> 
> 
>> On Jul 11, 2021, at 11:16 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> On 7/11/21 5:53 PM, Shawn McKinney wrote:
>>>
>>>> On Jul 11, 2021, at 9:42 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
>>>>
>>>> I do think that we need some faster way to validate the packages. It took me around 1h30 to do that last night, most of it being waiting for the tests to be ran.
>>>
>>> By tests you mean integration tests, i.e. junit?
>>>
>>> If yes, that’s surprising.  It runs in about 7 or 8 minutes for me.
>>
>> The tests against ApacheDS are quite slow and also take more than one
>> hour for me. See also the Jenkins build [3] which most of the time only
>> runs the IT once and fails with some timing issues.
>>
> 
> Yes, the tests are quite intense with many thousands of edits being sent.  Hopefully, with the changes to use its new DB (get finished), this will speed up.
> 
> In the meantime, perhaps I should create an abbreviated test.  One that can finish in under 10 minutes.

I don't really mind if the tests are taking 10 mins or even 1 hour, my 
problem is that there are many manual steps involved and I would like to 
see iff we can just start a script that ends in, say, 1h and says=: "Ok, 
  builds done, sig verified, N&L checked, all is good" without having 
anything to do but to have a good tea and enjoy a Dr House in the mean 
time :-)

> 
>>> What test suite are you running?
>>>
>>>> Can we design a script that does all the steps automatically, including the signature verifications and N&L checks?
>>>>
> 
> Just getting back to this.  What does the script need to do?
> 
> 1. Build the packages
> 2. Run the core integration tests
> 3. Check the sigs.
> 4. N&L checks?  How do we automate this?

N&L checks would mainly be checking that the packages contain them.

> 
> And, what should it be written in — Bash?

Yes, or whatever works.


-- 
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecharny@busit.com https://www.busit.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org


Re: [RESULT] [VOTE] Apache Fortress 2.0.6 release (take 2)

Posted by Shawn McKinney <sm...@apache.org>.

> On Jul 11, 2021, at 11:16 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
> 
> On 7/11/21 5:53 PM, Shawn McKinney wrote:
>> 
>>> On Jul 11, 2021, at 9:42 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
>>> 
>>> I do think that we need some faster way to validate the packages. It took me around 1h30 to do that last night, most of it being waiting for the tests to be ran.
>> 
>> By tests you mean integration tests, i.e. junit?
>> 
>> If yes, that’s surprising.  It runs in about 7 or 8 minutes for me.
> 
> The tests against ApacheDS are quite slow and also take more than one
> hour for me. See also the Jenkins build [3] which most of the time only
> runs the IT once and fails with some timing issues.
> 

Yes, the tests are quite intense with many thousands of edits being sent.  Hopefully, with the changes to use its new DB (get finished), this will speed up.

In the meantime, perhaps I should create an abbreviated test.  One that can finish in under 10 minutes.

>> What test suite are you running?
>> 
>>> Can we design a script that does all the steps automatically, including the signature verifications and N&L checks?
>>> 

Just getting back to this.  What does the script need to do?

1. Build the packages
2. Run the core integration tests
3. Check the sigs.
4. N&L checks?  How do we automate this?

And, what should it be written in — Bash?

>>> I mean, technically, it's a no brainer, but from the validation PoV, could we assume that running the script and get a positive response as a 'Good to Go' signal ?
>> 
>> I don’t see why not.  The question, is how to manage the platform specifics of the target.  
>> 
>> I’ve been using Ansible which creates a new fortress env by scratch.  Currently, it sets up OpenLDAP for the run, adding apacheDS has been on my todo list for some time.
>> 
>> Could add a playbook for validating the packages.
>> 
>> Open to ideas here.
> 
> There already exist two scripts to run the fortress-core intgraion tests
> against ApacheDS [1] or OpenLDAP [2]. Those are also used in the Jenkins
> builds [3][4]. Both require a a Docker installation though.


---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org


Re: [RESULT] [VOTE] Apache Fortress 2.0.6 release (take 2)

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
On 7/11/21 5:53 PM, Shawn McKinney wrote:
> 
>> On Jul 11, 2021, at 9:42 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
>>
>> I do think that we need some faster way to validate the packages. It took me around 1h30 to do that last night, most of it being waiting for the tests to be ran.
> 
> By tests you mean integration tests, i.e. junit?
> 
> If yes, that’s surprising.  It runs in about 7 or 8 minutes for me.

The tests against ApacheDS are quite slow and also take more than one
hour for me. See also the Jenkins build [3] which most of the time only
runs the IT once and fails with some timing issues.

> What test suite are you running?
> 
>> Can we design a script that does all the steps automatically, including the signature verifications and N&L checks?
>>
>> I mean, technically, it's a no brainer, but from the validation PoV, could we assume that running the script and get a positive response as a 'Good to Go' signal ?
> 
> I don’t see why not.  The question, is how to manage the platform specifics of the target.  
> 
> I’ve been using Ansible which creates a new fortress env by scratch.  Currently, it sets up OpenLDAP for the run, adding apacheDS has been on my todo list for some time.
> 
> Could add a playbook for validating the packages.
> 
> Open to ideas here.

There already exist two scripts to run the fortress-core intgraion tests
against ApacheDS [1] or OpenLDAP [2]. Those are also used in the Jenkins
builds [3][4]. Both require a a Docker installation though.

Kind Regards,
Stefan

[1]
https://github.com/apache/directory-fortress-core/tree/master/src/docker/apacheds-for-apache-fortress-tests
[2]
https://github.com/apache/directory-fortress-core/tree/master/src/docker/openldap-for-apache-fortress-tests
[3]
https://ci-builds.apache.org/job/Directory/job/dir-fortress-core-docker-apacheds-test/
[4]
https://ci-builds.apache.org/job/Directory/job/dir-fortress-core-docker-openldap-test/

---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org


Re: [RESULT] [VOTE] Apache Fortress 2.0.6 release (take 2)

Posted by Shawn McKinney <sm...@apache.org>.
> On Jul 11, 2021, at 9:42 AM, Emmanuel Lécharny <el...@gmail.com> wrote:
> 
> I do think that we need some faster way to validate the packages. It took me around 1h30 to do that last night, most of it being waiting for the tests to be ran.

By tests you mean integration tests, i.e. junit?

If yes, that’s surprising.  It runs in about 7 or 8 minutes for me.

What test suite are you running?

> Can we design a script that does all the steps automatically, including the signature verifications and N&L checks?
> 
> I mean, technically, it's a no brainer, but from the validation PoV, could we assume that running the script and get a positive response as a 'Good to Go' signal ?

I don’t see why not.  The question, is how to manage the platform specifics of the target.  

I’ve been using Ansible which creates a new fortress env by scratch.  Currently, it sets up OpenLDAP for the run, adding apacheDS has been on my todo list for some time.

Could add a playbook for validating the packages.

Open to ideas here.

Thanks for the idea

—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org


Re: [RESULT] [VOTE] Apache Fortress 2.0.6 release (take 2)

Posted by Emmanuel Lécharny <el...@gmail.com>.
Thanks for the hard work, Shawn!

I do think that we need some faster way to validate the packages. It 
took me around 1h30 to do that last night, most of it being waiting for 
the tests to be ran.

Can we design a script that does all the steps automatically, including 
the signature verifications and N&L checks?

I mean, technically, it's a no brainer, but from the validation PoV, 
could we assume that running the script and get a positive response as a 
'Good to Go' signal ?

Thanks !

On 11/07/2021 15:33, Shawn McKinney wrote:
> Closing with 3 binding votes, Stefan, Emmanuel and my +1.
> 
> Thanks
> 
> —
> Shawn
> 
>> On Jul 11, 2021, at 4:15 AM, Stefan Seelmann <ma...@stefan-seelmann.de> wrote:
>>
>> +1
>>
>> Checked the licenses.
>> Checked the signatures and checksums.
>> Built all 4 projects with Java 11.
>> Run the Apache Fortress Core Integration Test against OpenLDAP.
>>
>> Kind Regards,
>> Stefan
>>
>> On 7/11/21 5:49 AM, Emmanuel Lécharny wrote:
>>> Checked the release,
>>> checked the signaturre,
>>>
>>> +1 from me !
>>>
>>> On 08/07/2021 20:56, Stefan Seelmann wrote:
>>>> FYI, I won't have time before Sunday to check the release.
>>>>
>>>> On 7/6/21 8:57 PM, Shawn McKinney wrote:
>>>>> I have removed (and verified) the jboss jar dependency from fortress
>>>>> rest.  The repos are retagged. Artifacts rebuilt and staged once
>>>>> again. Let’s try this again...
>>>>>
>>>>>
>>>>> Hello,
>>>>>
>>>>> This is an announcement to vote for the next release of Apache
>>>>> Directory Fortress, 2.0.6.
>>>>>
>>>>> Here are the list of bugs and enhancements:
>>>>>
>>>>> https://issues.apache.org/jira/projects/FC/versions/12349361
>>>>>
>>>>> A tag created for git: ‘2.0.6', and the sources may be pulled using
>>>>> git commands:
>>>>> git clone --branch 2.0.6
>>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-core.git
>>>>> git clone --branch 2.0.6
>>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-realm.git
>>>>> git clone --branch 2.0.6
>>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-enmasse.git
>>>>> git clone --branch 2.0.6
>>>>> https://git-wip-us.apache.org/repos/asf/directory-fortress-commander.git
>>>>>      
>>>>> with their associated checksums:
>>>>> - core:  33ac2682170e26272cdc05b370f6c1ffcd834edc
>>>>> - realm: f4777d0842e4a93ad35b4f2ed3d00d9d185728ed
>>>>> - rest:  35a96e40030182a99a4c8cd9effad5ddc0b4bc45
>>>>> - web:   647356f53fcc9406d434fee8a0d13123dbcde510
>>>>>
>>>>> Or, source and binary distros may be downloaded from SVN:
>>>>> - https://dist.apache.org/repos/dist/dev/directory/fortress/2.0.6/
>>>>>
>>>>> The staging repo on Nexus:
>>>>> -
>>>>> https://repository.apache.org/content/repositories/orgapachedirectory-1203
>>>>>
>>>>>
>>>>> Test against LDAP using one of these:
>>>>> -
>>>>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-APACHEDS.md
>>>>>
>>>>> -
>>>>> https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-DOCKER-SLAPD.md
>>>>>
>>>>>
>>>>> - Choose one of the above.  Complete (only) the sections leading up
>>>>> to and including the SECTION entitled: 'Apache Fortress Core
>>>>> Integration Test’
>>>>>
>>>>> Please vote:
>>>>> [ ] +1   | Release Fortress 2.0.6
>>>>> [ ] +/-0 | Abstain
>>>>> [ ] -1   | Do *NOT* Release Fortress 2.0.6
>>>>>
>>>>>
>>>>> —
>>>>> Shawn
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
>>>>> For additional commands, e-mail: dev-help@directory.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
>>>> For additional commands, e-mail: dev-help@directory.apache.org
>>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@directory.apache.org
>> For additional commands, e-mail: dev-help@directory.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
> For additional commands, e-mail: fortress-help@directory.apache.org
> 

-- 
*Emmanuel Lécharny - CTO* 205 Promenade des Anglais – 06200 NICE
T. +33 (0)4 89 97 36 50
P. +33 (0)6 08 33 32 61
emmanuel.lecharny@busit.com https://www.busit.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: fortress-unsubscribe@directory.apache.org
For additional commands, e-mail: fortress-help@directory.apache.org