This site is in read only mode. Please continue to browse, but replying, likes, and other actions are disabled for now.

⚠️ We've moved!

Hi there!

To reduce project dependency on 3rd party paid services the StackStorm TSC has decided to move the Q/A from this forum to Github Discussions. This will make user experience better integrated with the native Github flow, as well as the questions closer to the community where they can provide answers.

Use 🔗 Github Discussions to ask your questions.

Continuous integration for Packs with Jenkins

Platform Pack Management
#1

Has anyone used Jenkins to set up continuous integration for Packs?

Specifically, I’m wondering how best to set up tests that require Mongo and ST2 source code. I had a look at the Exchange CI repo and it appears that the CI pipeline starts up Mongo in a Docker container and then clones the ST2 source code, installs its Python dependencies, installs runners - https://github.com/StackStorm-Exchange/ci/blob/master/.circle/Makefile#L208 (I don’t understand what this does exactly) and then runs tests that attempt to register pack’s contents as well as run other lint scripts and pack unit tests.

I’m wondering: Can this be more easily done by using st2-docker on a Jenkins agent? Would this eliminate the need to manually set up the StackStorm environment (starting a Mongo container, installing ST2 runners, etc.)?

1 Like
#2

I have some experience with doing my own pack CI. Before I say anything - why are you trying to accomplish? Testing? Linting? Releases? All of the above?

#3

Do you wish to avoid circleci?

#4

Hi @punkrokk.

Right now, I want to accomplish testing and linting. Releases would be great, but not realistic at the moment.

CirclCI may be an option, but I have not explored it. Jenkins is a known viable option for me.