Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Make dev and staging libraries default to upstream

Avatar

Avatar
Validate 1
MVP
Jennifer_Kunz
MVP

Likes

313 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Contributor
Seeker
Shape 10
Shape 1
View profile

Avatar
Validate 1
MVP
Jennifer_Kunz
MVP

Likes

313 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Contributor
Seeker
Shape 10
Shape 1
View profile
Jennifer_Kunz
MVP

06-03-2019

Currently, if there is no library assigned to a dev or staging environment, it 404s. This can (reasonably) bother developers and break analytics testing on dev/staging/QA servers.

Ideally, if an environment does NOT have a library currently on it, it would just use whatever is currently upstream in prod.

4 Comments

Avatar

Avatar
Applaud 5
Level 1
lulufrancis
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Applaud 5
View profile

Avatar
Applaud 5
Level 1
lulufrancis
Level 1

Likes

0 likes

Total Posts

2 posts

Correct Reply

0 solutions
Top badges earned
Applaud 5
View profile
lulufrancis
Level 1

06-03-2019

Adding an option to allow enable/disable upstream would be helpful as well.

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

139 likes

Total Posts

310 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

139 likes

Total Posts

310 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

16-04-2019

We had some Akamai problems in the past that led to Dev Libraries being removed when they shouldn't be, but that has been fixed now.  The only time an Environment should ever return a 404 now is when it is first created and has never been built in.  And defaulting to Prod often wouldn't help in that scenario because it wouldn't have anything in it either.

One idea that has been floated is that when an Environment is created, we just drop an empty build there so that it wouldn't 404.  Curious to hear people's thoughts.

Avatar

Avatar
Validate 1
MVP
Jennifer_Kunz
MVP

Likes

313 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Contributor
Seeker
Shape 10
Shape 1
View profile

Avatar
Validate 1
MVP
Jennifer_Kunz
MVP

Likes

313 likes

Total Posts

81 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Contributor
Seeker
Shape 10
Shape 1
View profile
Jennifer_Kunz
MVP

16-04-2019

I think that'd be great, as a bare minimum.

Avatar

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

139 likes

Total Posts

310 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile

Avatar
Contributor
Employee
thebenrobb
Employee

Likes

139 likes

Total Posts

310 posts

Correct Reply

82 solutions
Top badges earned
Contributor
Seeker
Shape 1
Give Back 3
Give Back
View profile
thebenrobb
Employee

18-02-2020

Building empty libraries for new environments is on the roadmap for this year.

Status changed to: Accepted