What are the Slack Archives?
It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
someone has a clue why scheduler:suspend did not stop jenkins? I got the feedback Scheduler Name: je
Comments
-
as far as I know it will stop when the process is done - probably it is still running
0 -
i guess it will finish the running jobs
0 -
dang… too late 😊
0 -
that command does not stop jenkins, it is just disables jobs
0 -
And without specifying store within the command it will terminate jobs only for default store.
0 -
that is interesting 🤔
0 -
will it tell that?
0 -
it DOES say which environment and store it runs for, every time I think
0 -
so if i have 5 stores i have to run this command for every shop?
0 -
yes, for every
0 -
with APPLICATION_STORE=STORE?
0 -
yes
0 -
so I did one hour ago but still running
0 -
can you manually kill the jobs in the dashboard?
0 -
Would you able to check if jobs are disabled after running that command? via Jenkins UI
0 -
with the se:je:di i got jenkins shutting down
0 -
but now it seems it was shutting down
0 -
thank you
0 -
but not for the main shop
0 -
ok, now it is stopped
0 -
ok, dunno why but they restart automatically...
0 -
it seems jobs are not disabled
0 -
i re added the old command and i get "Jenkins wird heruntergefahren"
0 -
maybe wrong configuration at my side or bug?
0 -
setup:jenkins:*? in this case you need to return configuration for setup module.0 -
we updated from old demo shop to the newest suite. normally we used setup:jenkins:* but in new version it is deprecated so we switched to scheduler. We followed the integration https://documentation.spryker.com/feature_integration_guides/spryker_in_docker/scheduler-feature-integration-201907.htm but it seems it is nor working properly. We readded the old setup:jenkins:* console command and it is working
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 930 Developer Corner
- 788 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K 📜 Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random