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..
quick question: `setup:jenkins:generate` was removed in
quick question:setup:jenkins:generate
was removed in https://github.com/spryker/setup/compare/4.1.2...4.2.0 but that caused our jenkins to fail with atomic deployment since the release folder (which jenkins knew about few releases ago) doesn't exist anymore. How is jenkins updated now?
Comments
-
Hi Jan,
Those commands was not deleted, but deprecated. The only way to remove those commands is changing ConsoleDependencyProvider.
What is your upgrade case?
0 -
0
-
ok, but the code says it was deprecated without replacement, so that means there's another way of seting up jenkins now, right?
my guess it's about scheduler:setup from now on, but that doesn't seem to work0 -
and @ULYHPR789 I see in spryker-shop/suite repo the consoledependencyprovider doesn't include jenkins commands anymore so in default implementation is has been removed, not ONLY deprecated
0 -
In shops, the deprecated plugins replaced with the new ones. And the new ones provides
scheduler:*
commands.0 -
Anyway letβs check your error.
0 -
It seems it is connected with CSRF protection. Check if you Jenkins has it turned on.
0 -
isn't that by-default-enabled security feature?
0 -
As far as I know it is turned off in official docker image.
Anyway if you have it turned on in Jenkins, you should set the appropriate config parameter, e.g.:
0 -
those are already configured in
config/Shared/config_default-development.php
0 -
SchedulerJenkinsConfig::SCHEDULER_JENKINS_CSRF_ENABLED => true
too?0 -
yes
0 -
Is it possible that Jenkins has CSRF turned off?
0 -
no
0 -
well if it did it would throw
Exception: Cannot generate CSRF token. Please check that CSRF protection is enabled on Jenkins server.
π0 -
my config is set to => false though
0 -
so just to confirm:
jenkins has csrf disabled and it is set toSchedulerJenkinsConfig::SCHEDULER_JENKINS_CSRF_ENABLED => false
in my config0 -
ah, makes sense, it is disabled in config, but not in the process, let me see if I can restart it
0 -
ok, so the problem seems to be the crumbissuer
0 -
if I set crumbissuer to false, then scheduler:setup runs fine
0 -
Looks similar to https://github.com/spinnaker/spinnaker/issues/2067
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
- 929 Developer Corner
- 787 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