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..
Hi there & hi @UMYJ4L2TX. is there any new module likely
Hi there & hi @UMYJ4L2TX.
is there any new module likely https://github.com/spryker/scheduler-jenkins/ in planning?
For example: https://github.com/spryker/scheduler-cron/ ?
Comments
-
Hi Marcus, I'm not aware about such plans but will clarify with our product team.
0 -
Thanks!
No one wants to use the "jenkins" only as a water heater or the right to run jobs / schedules. π0 -
π
0 -
Hi Marcus,
I am the product manager responsible for our docker solution, and I am happy to help you.
We are planning to work on a smaller and more lightweight solution for managing jobs.
And, I highly appreciate you sharing your thoughts about the desired solution:
β’ what kind of issues you have with Jenkins today
β’ what would you like to improve
β’ what is missing or you want to addPlease, feel free to answer here or reach me via DM or Email.
0 -
Hi Dmytro, I'm planning just add the crons manually (as they are not changing often for us). But my main requirement is that we need different jobs on different zed instances, as we have one which is dedicated for data import handling - therefore called zimp - and another instance handling user requests. I implemented some green/blue deployment which results in zimp using the new codebase to import, publish & sync data. meanwhile al user- related stuff is handled via the old codebase in the regular zed. Therefore having just 1 instance of jenkins is a little pita... But i guess building something which takes this complexity into account may not be worth it, as setting up cronjobs isn't that hard in the first place...
0 -
Hi Georg,
Have you splitted the jobs for performance sake (distributing the load between 2 jenkins or crons) or because zed instances are working with different databases?
0 -
They are working with the same db, but (during import, esp. after a deployment which changes the structure of the data synchronized) with different elasticsearch indices (where an alias is changed on activation) and redis dbs (which then are swapped on activation). Therefore we can near-instant swap redis, search and the codebases and avoid downtime. This is needed, because our import cycle is about 4 hours. Otherwise we would have a downtime of this length during deployment... Also it has the benefit of separating the user-experience of performance from the load the import produces for the server at least...
0 -
@UMVENKCBF, sure you meant me? π
0 -
Hi Danielo, you were mentioned because you were named as contact person for "devops" and you are responsible for customer success π
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 75 Spryker News
- 924 Developer Corner
- 783 Spryker Development
- 88 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
- 25 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