I released an update to my first Android application developed Give Me Numbers.
User Interface Improved, more colorful
You can choose a separator for the numbers generated
I released an update to my first Android application developed Give Me Numbers.
User Interface Improved, more colorful
You can choose a separator for the numbers generated
After being a PMP certified the next challenge was for sure the Scrum Master certification. A different challenge but it deserved a try.
After reading several books, training hundreds of questions… the effort brought its results.
Soon I will detail here the books I read a and still do, for the certification.
I just developed the visual studio code version of the InHash plugin already developed for IntelliJ and Eclipse.
This plugin computes hash and checksum for files and selected text.
It started to be a necessity for a project where I was involved and “why not to create a plugin from it?”
Find it here: Visual Studio Code Extension to compute Hashs and Checksum
I just developed the eclipse version of the InHash plugin already developed for IntelliJ.
This plugin computes hash and checksum for files and selected text.
It started to be a necessity for a project where I was involved and “why not to create a plugin from it?”
Find it here: InHash – Eclipse plugin to compute hash and checksum
I just developed a plugin for IntelliJ.
The plugin computes hash and checksum for files and selected text.
It started to be a necessity for a project I was involved and “why not to create a plugin from it?”
Find it here: InHash – Intellij plugin to compute hash and checksum
This question arises frequently.
There is no only markdown way to do it. We add a little html in the markdown.
1 2 3 4 5 |
| column1 | column2 | | ------------: | :------------ | | value column1 | value column2 | | second value | <ul><li>list item 1</li><li>list item 2</li></ul> | | another row | another row in second column | |
java.lang.NoClassDefFoundError: com/fasterxml/jackson/annotation/JsonInclude$Value
If this error occurs try addind the following dependencies to your pom.xml
Usually jackson needs these 3 dependencies:
com.fasterxml.jackson.core jackson-databind 2.9.0 com.fasterxml.jackson.core jackson-core 2.9.0 com.fasterxml.jackson.core jackson-annotations 2.9.0
Straight to the point:
You need at least these dependencies:
org.junit.jupiter junit-jupiter-api 5.1.0 test org.junit.jupiter junit-jupiter-engine 5.1.0 test
There are other dependencies for IDEs and older versions of jUnit if you need them:
org.junit.vintage junit-vintage-engine 5.1.0 test org.junit.platform junit-platform-launcher 1.1.0 test org.junit.platform junit-platform-runner 1.1.0 test
With the big wave of DevOps, Pipelines are one of the most used words. Why? Because continuous integration and continuous delivery are about pipelines.
Jenkins is one of the most used components in a Continuous Integration environment, and its community decided to take into this wave too. How?
Well, redefining how the pipelines are configured and developed in Jenkins.
The new pipelines are developed using Groovy Language, which opens a very wide spectrum of possibilities of configurations to the integration process. (so… who said Groovy lang was dying?)
There are 2 ways of developing pipelines in Jenkins, the Declarative and the Scripted way
In the Scripted approach you use the full power of Groovy language, however, the blue ocean plugin will not be used as expected and you cant visualize the pipeline. More on this later.
node { stage('chekout from git') { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[]] ]) try { sh 'mvn test' } catch (e) { currentBuild.result = 'FAILURE' throw e } finally { cleanWs cleanWhenFailure: false } } stage('build the project') { steps { sh 'mvn -B -DskipTests clean package' } } }
But it’s the declarative way that draws the pipeline flow as we expected.
This approach brings first an elegant structure of the code and the use of the Blue Ocean plugin where we will visualize the pipeline flow, literally!
An example of a declarative pipeline can be something like this:
pipeline { agent none stages { stage('chekout from git') { steps { checkout([$class: 'GitSCM', branches: [[name: '*/master']], doGenerateSubmoduleConfigurations: false, extensions: [], submoduleCfg: [], userRemoteConfigs: [[]] ]) } } stage('build the project') { steps { sh 'mvn -B -DskipTests clean package' } } } }
If you install the Blue Ocean plugin and run a declarative pipeline you will see something like this:
(this example was taken from Jenkins website)
So, should I use Declarative or Scripted Pipelines?
– Scripted Pipelines use the full Groovy language, but you will not have the enhanced visualization.
– Well, declarative is a little more restricted in the structure of the code, but you can always use the step “script {
The Jenkins website as a good tutorial to follow, please visit it to move forward in this technology.
Hope this post was enough to capture your attention about how Jenkins can have a really beautiful and useful visualization of a pipeline.
Bad Behavior has blocked 219 access attempts in the last 7 days.
Hyper Smash