Git Product home page Git Product logo

vsts-jboss-wildfly's Introduction

This extension provides build tasks to manage and deploy WAR and EAR file to JBoss Enterprise Application Platform (EAP) 7 or WildFly 8 and above.

This extension installs the following components:

  • A service endpoint for connecting to JBoss EAP 7 and WildFly 8 and above.
  • A build task to run commands over HTTP management endpoint.
  • A build task to deploy your WAR and EAR files to JBoss EAP 7 and WildFly 8 and above.

Create a JBoss EAP / WildFly Connection

  • Make sure the application server's management http interface is exposed and can be reached over the network.
  • Skip this step if you are on Team Foundation Server 2015 and enter the credentials directly on the task.
  1. Open the Services page in your Visual Studio Team Services Control Panel

  2. In the New Service Endpoint list, choose "JBoss and WildFly"

    WildFly/JBoss EAP Endpoint

  3. Create a "JBoss and WildFly" Service Endpoint and specify your JBoss EAP 7 or WildFly 8+ management URL, username and password.

    WildFly/JBoss EAP Endpoint

Manage JBoss and WildFly servers over http

  1. Open your build definition and add the "JBoss EAP / WildFly Management CLI" task. The task can be found in the "Utility" section.

    WildFly/Mangement task

  2. Select the "JBoss and WildFly" service endpoint you created previously, or enter the credentials.

  3. Enter commands to be executed, one command per line.

Deploy applications to JBoss EAP 7 and WildFly 8 and above

  1. Open your build definition and add the "JBoss EAP / WildFly Deployer CLI" task. The task can be found in the "Deploy" section.

    WildFly/Deployment task

  2. Select the "JBoss and WildFly" service endpoint you created previously, or enter the credentials.

  3. Enter the file to be deployed (a wildcard is allowed but it must resolve to exactly one file).

  4. Select and enter other optional fields. Hover over the info icon at the end of each field for additional help.

Deploy applications to JBoss EAP 6

Please refer to this guide.

Learn more

For detailed instructions on setting up a build definition, check out this guide.

Check out this guide for an overview of extensions of Visual Studio Team Services.

For detailed instructions on how to get and install extensions, check out this guide

Create a WildFly instance on Azure

Microsoft Azure provides pre-configured WildFly images. Create your free Azure account if you do not have an Azure account.

License

The code is open sourced under the MIT license. We love and encourage community contributions.

Contributing

How to build.

vsts-jboss-wildfly's People

Contributors

lsprado avatar microsoft-github-policy-service[bot] avatar xzhe avatar yacaovsnc avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

vsts-jboss-wildfly's Issues

Deprecation warning

A deployment pipeline in Azure DevOps Server using this task produces this warning:

##[warning]This task uses Node 6 execution handler, which will be removed March 31st 2022. If you are the developer of the task - please consider the migration guideline to Node 10 handler - https://aka.ms/migrateTaskNode10 (check this page also if you would like to disable Node 6 deprecation warnings). If you are the user - feel free to reach out to the owners of this task to proceed on migration.

And maybe Node 10 would not be the right choice either...
I am just a user of the task, not a TypeScript developer, but please let me know if I can help with this migration.

Should be using different CLI.connect() method.

We use https-remoting for all our JBoss/Wildfly remoting calls and this plugin doesn't work.
It looks to be due to the wrong CLI.connect() method being used.

In:
com.microsoft.alm.Driver

You are calling the CLI using the connect method at line 151 which defaults to http-remoting
https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/java/org/jboss/as/cli/scriptsupport/CLI.java#L151

You should be using the connect method at line 178 - which allows you to specifiy the protocol (http-remoting or https-remoting)
https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/java/org/jboss/as/cli/scriptsupport/CLI.java#L178

Ref:
https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/java/org/jboss/as/cli/scriptsupport/CLI.java#L170

It should probably be specifying the protocol. As using https-remoting is more secure, versus defaulting to http-remoting. Using the connect method at line 178 allows you to use either.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.