[Improve][SeaTunnel-Web] Change JobStatus to enum type to avoid hard coding

[wuchunfu]

Purpose of this pull request

Change JobStatus to enum type to avoid hard coding

Check list

• Code changed are covered with tests, or it does not need tests for reason:
• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs

[Hisoka-X]

Please fix ci. cc @arshadmohammad

[wuchunfu]

@Hisoka-X @arshadmohammad PTAL, thanks

[arshadmohammad]

Many integration tests will fail after this change. @wuchunfu can you run the integration tests. Here is the command to run the integration tests

./mvnw -T 1C -B verify -DskipUT=true -DskipIT=false -DSEATUNNEL_HOME=/some/path/apache-seatunnel-2.3.7 -DST_WEB_BASEDIR_PATH=seatunnel-web-dist/target/apache-seatunnel-web-1.0.2-SNAPSHOT/apache-seatunnel-web-1.0.2-SNAPSHOT

[wuchunfu]

Many integration tests will fail after this change. @wuchunfu can you run the integration tests. Here is the command to run the integration tests

./mvnw -T 1C -B verify -DskipUT=true -DskipIT=false -DSEATUNNEL_HOME=/some/path/apache-seatunnel-2.3.7 -DST_WEB_BASEDIR_PATH=seatunnel-web-dist/target/apache-seatunnel-web-1.0.2-SNAPSHOT/apache-seatunnel-web-1.0.2-SNAPSHOT

@arshadmohammad Thank you for your review. My testing is normal. Are you sure it was caused by my changes? If that's the case, is there a problem with CI? Can you fix it?

[wuchunfu]

I didn't find any problems during my testing here

[Hisoka-X]

Many integration tests will fail after this change. @wuchunfu can you run the integration tests. Here is the command to run the integration tests
./mvnw -T 1C -B verify -DskipUT=true -DskipIT=false -DSEATUNNEL_HOME=/some/path/apache-seatunnel-2.3.7 -DST_WEB_BASEDIR_PATH=seatunnel-web-dist/target/apache-seatunnel-web-1.0.2-SNAPSHOT/apache-seatunnel-web-1.0.2-SNAPSHOT

@arshadmohammad Thank you for your review. My testing is normal. Are you sure it was caused by my changes? If that's the case, is there a problem with CI? Can you fix it?

We didn't bring test case into ci at now. We should add it.

[arshadmohammad]

@wuchunfu In your attached snapshot I can not see how many tests are run, how many failed or passed, can you please attach snapshot like below

Here I can see 42 tests are run, 0 failed, 0 error, 0 skipped.

[Hisoka-X]

@wuchunfu In your attached snapshot I can not see how many tests are run, how many failed or passed, can you please attach snapshot like below

Here I can see 42 tests are run, 0 failed, 0 error, 0 skipped.

Hi @arshadmohammad , does our test case need rely mysql container? If not, let me add it into ci.

[arshadmohammad]

The integration test cases are dependent on both MySQL and the Seatunnel-Engine.

1. Runtime mysql is being added as part of [Improvement][Seatunnel-web] Add mysql environment in e2e test cases. seatunnel#7403 to avoid dependency on external mysql.
   I will start working on this, so we can run IT test cases in CI environment.
2. Integration tests also require seatunnel-engine which should be available in CI environment.

[Hisoka-X]

I will start working on this, so we can run IT test cases in CI environment.

Thanks @arshadmohammad ! You can refer https://github.com/apache/seatunnel/blob/dev/.github/workflows/build_main.yml and apache/seatunnel#5495. We implemented the logic to run CI in forked repositories so that devs can trigger CI themselves instead of maintainers manually triggering it every time.

Integration tests also require seatunnel-engine which should be available in CI environment.

Yes, we can use github action actions/checkout@v4.

[wuchunfu]

@wuchunfu In your attached snapshot I can not see how many tests are run, how many failed or passed, can you please attach snapshot like below

Here I can see 42 tests are run, 0 failed, 0 error, 0 skipped.

@arshadmohammad PTAL, thanks

[arshadmohammad]

LGTM +1