Articles

Running Self-Hosted GitLab Pages Behind Reverse Proxy and In a Separate Server

,

GitLab Pages is a way to create websites for projects and groups in order to publish documentation, wikis, or any static content. Sometimes, for resource limitation, decreasing the load on the main GitLab instance (if self-hosted), to increase security, or for separating docs and wikis from code, we need to host our GitLab Pages in a separate server. To achieve this, we should have two GitLab instance on two distinct machines: one of them is our main GitLab (a normal GitLab installation) and the other one is an instance only for publishing GitLab Pages.

This is a tutorial and provides some technical information and configurations, We assume you are familiar with GitLab installation and GitLab Pages, and already have one GitLab self-managed instance (on-premises or in the cloud) in use.

Source de l’article sur DZONE

/par

DevOps Security at Scale (Part 1): Security Policy as Code

,

This is the first installment in a series of blog posts on this topic.

Years have passed since the software world first gasped at the high-velocity achievements of Netflix, Etsy, Flickr, and others, watching in awe as they shipped features in less time than other companies could even begin to start planning them. The secrets to their success were collectively characterized as “DevOps” – a new approach to delivering software that focused intensely on continuous integration, continuous delivery, and breaking down barriers between engineering and operations teams in order to ship faster, and with less risk.

Source de l’article sur DZONE

/par

Serenity Ensure – Fluent Assertions in Serenity Screenplay

,

Assertions are an important part of any test automation framework, and Serenity gives us many options. You can, of course, use standard JUnit, Hamcrest or AssertJ assertions at any point in a Screenplay test. But more recent versions of Serenity Screenplay provide an alternative approach, which many developers find easier to use and faster to write: the serenity-ensure module.

Introducing serenity-ensure

The Ensure class produces a Performable, so you can integrate them directly into the attemptsTo() method. It also has a very readable DSL and lets you use code completion to discover the assertions you can use for different values, making writing assertions easier and quicker.

Source de l’article sur DZONE

/par

Tom’s Tech Notes: How to Innovate Better [Podcast]

, ,

Welcome to our latest episode of Tom’s Tech Notes! This week, DZone.com’s research analyst Tom Smith chats with Dell Boomi CTO Michael Morton about how to innovate better. Learn who to approach about innovating, how to plan for it, and the importance of not just failing fast, but learning and implementing fast.

And, as always, you can find our podcasts on:

Source de l’article sur DZONE

/par

The Value of Security Testing in QA

,

Over in the TechWell Hub, I was recently asked by a fellow community member, "Is there value in having traditional testers do security testing in addition to the testing taking place from our security group?" I thought it was a great question, and it deserves a more detailed response.

For many organizations, traditional software and testing groups are separated from the IT security group. The first is just concerned with functionality, while the latter cares only about security. In many cases this results in adversarial relationships, which almost always leads to some challenges for software development teams:

Source de l’article sur DZONE

/par

Tom’s Tech Notes: Microservices Use Cases [Podcast]

,

Welcome to our latest episode of Tom’s Tech Notes! In this episode, Tom asks what our collection of industry experts’ favorite use cases and benefits of microservices are. 

As a primer and reminder from our initial post, these podcasts are compiled from conversations our analyst Tom Smith has had with industry experts from around the world as part of his work on our research guides.

Source de l’article sur DZONE

/par

5 Reasons Why Continuous Delivery Is Worth a Shot

,

Image titleHave you been on after-hours production support on a Friday night following a massive software feature release? Sweaty palms and nervous jitters with crossed fingers are all the sensations you feel when multiple features are being released, while missing being on a beach or being at a party with friends and family.

How can we avoid this and make our releases predictable? Here are five reasons why “continuous delivery” is the right solution for making our lives for people in software easier and drive a better experience for our customers.

Source de l’article sur DZONE

/par

Automated Testing: Facilitating Continuous Delivery

,

It’s no surprise that more organizations are making the shift from manual to automated testing — or that they’re incorporating testing earlier in the software development lifecycle. Automated testing is a significant step on the road to continuous delivery. Download this guide to learn when to implement test-driven development, how to automate mobile UI testing, how to use natural language processing to write automated tests in plain English, and much more.
Source de l’article sur DZONE

/par

Tom’s Tech Notes: Concerns With Containers [Podcast]

,

Welcome to our latest episode of Tom’s Tech Notes! In this episode, we’ll hear advice from a host of industry experts about how to secure your containers. Learn what they have to say about security, ease of use, ecosystem maturity, and the talent gap.

As a primer and reminder from our intial post, these podcasts are compiled from conversations our analyst Tom Smith has had with industry experts from around the world as part of his work on our research guides.

Source de l’article sur DZONE

/par

Enterprise-Grade QA on a Budget

,

We operate in a continuous delivery world in which a seamless customer experience is paramount. Regardless of whether you’re a global Fortune 500 organization or a fast-growing startup, failing to deliver a digital experience that delights your users is a critical mistake you can’t afford to make.

A chief challenge compounding today’s continuous delivery expectation is the growing amount of testing that has to be carried out. In the not-too-distant past, companies controlled all of their software, available on a single platform to a similar type of user with one uniform release cycle. Today’s landscape is vastly different, with websites and apps relying on a mix of modules and services under the control of various vendors, all with independent release cycles, in a heterogeneous platform environment with a wide range of user types.

Source de l’article sur DZONE

/par