Hi Luca,
Sorry for late reply.
I looked into the pipeline-smoke-test job.
* limited re-run capability and lack of graphical UI would not be critical.
* BRANCH/RELEASE seem not to be good a candidate for axis since
supported products and OS distributions are changing.
We should create job per release.
* In order to apply the pipeline for packaging,
it is crucial that we can downloading built artifacts of specific
configuration
regardless of success/failure of other configurations.
We can download artifacts from URL like following in our current multi
configuration job.
*
https://ci.bigtop.apache.org/job/Bigtop-trunk-x86_64/DISTRO=centos-7,PLATFORM=amd64-slave,PRODUCT=hadoop/lastSuccessfulBuild/artifact/*zip*/archive.zip
Thanks,
Masatake Iwasaki
On 2024/03/21 23:18, Luca Toscano wrote:
Hi Masatake,
Not sure if you saw https://issues.apache.org/jira/browse/BIGTOP-4058
but we could take some time to check also the experimental smoke test
pipelines for branch-3.3, lemme know what you think :)
Luca
On Tue, Mar 19, 2024 at 6:50 AM Masatake Iwasaki
<[email protected]> wrote:
I'm updating CI jobs for master branch now.
If the result of smoke-tests looks good,
I will create branch-3.3 and set up CI jobs creating release.
Masatake Iwasaki
On 2024/03/01 10:40, chenqiang2080 wrote:
Hi,all
The tasks of next Bigtop release 3.3 version(BIGTOP-3909) are
basically completed.
https://issues.apache.org/jira/browse/BIGTOP-3909
May I ask when Bigtop v3.3 release will start? And who is the release
manager?
As a contributor who finished the work support openEuler OS, i can do
some work for Bigtop pre-release testing.
Best Regards!
